[Glass] GsDevKit Server Blocks for Thin Client appications ... pre-announcement

[Mariano Martinez Peck via Glass]

On Wed, Apr 22, 2015 at 12:55 AM, Dale Henrichs <
dale.henrichs at gemtalksystems.com> wrote:

>
>
> On 4/21/15 7:01 PM, Mariano Martinez Peck wrote:
>
>
>
> On Thu, Apr 16, 2015 at 2:23 AM, Dale Henrichs via Glass <
> glass at lists.gemtalksystems.com> wrote:
>
>>  A GsDevKit Server Block[1] is a block that is written in-line in client
>> Smalltalk, but is executed in GemStone. For example the following
>> expression is executed in a standard Pharo workspace:
>>
>>   | shell x y |
>>   shell := TDShell forSessionNamed: 'devKit'.
>>   x := 3.
>>   y := 4.
>>   shell onServerDo: [ x + y ].
>>
>
>
>  Dale,
>
>  I know (because I already asked a few months/years ago) that from a
> stone X you can do a remote login on stone Y and execute stuff in Y. But
> now I wonder....could server blocks also work for gemstone-gemstone? (my
> gut feelings tell me that yes) I mean, could I run the above code from
> GemStone itself?   That would automatically resolve all the remote login
> stuff and the ston serialization.
>
> The short answer is yes.
>
> The long answer is that there is a bit of client-side code that is written
> in Pharo now that would have to be ported to GemStone. The bits that are
> specific to server blocks is a pretty small slice of code, but it is a
> chunk of code ...
>
>
OK, I see.


> I think I see where you are going with this - moving object graphs between
> stones?:)
>
>
Yes!

I guess the one sticking point is that it may not be quite as easy to
> automatically extract variable references from blocks, so it would probably
> make sense to just pass block args across the wire ... not quite as "fancy"
> but still very functional ...
>
>
Ok, I see.

Thanks Dale for the answer


-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150423/39e54e99/attachment.html>