Inter-image communication

>
> How would I, from one image, tell another image to execute something?
>
> I searched Google and the Squeak and Pharo lists for:
> - "[Pharo|Squeak] inter-image communication"
> - "[Pharo|Squeak] script"
>
> The results included various references to old projects that I never hear
> mentioned now, and instructions on how to run code (via a .st as an argument
> to the vm command line) when launching an image.
>
> Thanks.
> Sean
> --
> View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2320723.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> How would I, from one image, tell another image to execute something?
>
> I searched Google and the Squeak and Pharo lists for:
> - "[Pharo|Squeak] inter-image communication"
> - "[Pharo|Squeak] script"
>
> The results included various references to old projects that I never hear
> mentioned now, and instructions on how to run code (via a .st as an argument
> to the vm command line) when launching an image.
>
> Thanks.
> Sean
> --
> View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2320723.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>
> Stéphane Ducasse wrote:
>>
>> rst?
>> RemoteSmalltalk?
>>
>
> rst = RemoteSmalltalk = SO COOL!!!
>
> I easily shared objects from a Pharo 1.1 image with 4 other local images -
> including a Squeak 4.1 image!
>
>
> For a hoot:
>
> 1. In a Pharo 1.1 image with rST installed doit:
> "Transcript open.
> RSTSamples serverStartup"
>
> 2. In a Squeak 4.1 image with rST installed doit:
> "RSTBroker
> startOnPort: self clientPort
> logging: false.
>
> remoteTranscript := ('Transcript@' , self serverBrokerID) asLocalObject.
> remoteTranscript show: 'everything is ok! (from client side)';
> cr"
>
> 3. Pick up jaw after you see that the squeak image has sent a message to the
> Pharo image's Transcript, whose contents now appear as 'everything is ok!
> (from client side)'
>
> n.b. According to the docs, in both images, doit: "RSTBroker stop"
>
>
> How to load:
> I have no write access to rST, so the required packages can be loaded as
> follows:
> "Gofer new
> squeaksource: 'KomHttpServer';
> package: 'DynamicBindings';
> load.
>
> Gofer new
> squeaksource: 'KomHttpServer';
> package: 'KomServices';
> load.
>
> Gofer new
> squeaksource: 'SPDProjectUpdates';
> package: 'rST';
> load."
>
> Thanks for the pointer!
>
> 1.  This seriously frees me to play with objects in different forks and
> versions because I know I can beam the live objects to another image
> whenever I want, and not have them stranded.
> 2.  This seems like it should be perfect for scripting an image, but what
> shared object would allow arbitrary code to be run on the server?  I played
> with Workspace, but got lost down the delegation rabbit hole
>
> Sean
>
> p.s. I got it loading with minimal changes - just had to fix the underscore
> assignments, and break the dependency to an old version of KomServices.
> --
> View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2321673.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>
> St?phane Ducasse wrote:
>>
>> rst?
>> RemoteSmalltalk?
>>
>
> rst = RemoteSmalltalk = SO COOL!!!
>
> I easily shared objects from a Pharo 1.1 image with 4 other local images -
> including a Squeak 4.1 image!
>
>
> For a hoot:
>
> 1. In a Pharo 1.1 image with rST installed doit:
> "Transcript open.
> RSTSamples serverStartup"
>
> 2. In a Squeak 4.1 image with rST installed doit:
> "RSTBroker
>       startOnPort: self clientPort
>       logging: false.
>
> remoteTranscript := ('Transcript@' , self serverBrokerID) asLocalObject.
> remoteTranscript show: 'everything is ok! (from client side)';
>       cr"
>
> 3. Pick up jaw after you see that the squeak image has sent a message to the
> Pharo image's Transcript, whose contents now appear as 'everything is ok!
> (from client side)'
>
> n.b. According to the docs, in both images, doit: "RSTBroker stop"
>
>
> How to load:
> I have no write access to rST, so the required packages can be loaded as
> follows:
> "Gofer new
>       squeaksource: 'KomHttpServer';
>       package: 'DynamicBindings';
>       load.
>
> Gofer new
>       squeaksource: 'KomHttpServer';
>       package: 'KomServices';
>       load.
>
> Gofer new
>       squeaksource: 'SPDProjectUpdates';
>       package: 'rST';
>       load."
>
> Thanks for the pointer!
>
> 1.  This seriously frees me to play with objects in different forks and
> versions because I know I can beam the live objects to another image
> whenever I want, and not have them stranded.
> 2.  This seems like it should be perfect for scripting an image, but what
> shared object would allow arbitrary code to be run on the server?  I played
> with Workspace, but got lost down the delegation rabbit hole
>
> Sean
>
> p.s. I got it loading with minimal changes - just had to fix the underscore
> assignments, and break the dependency to an old version of KomServices.

> Does it work over a LAN?
>
> Hilaire
>
> Le 11/08/2010 20:17, Sean P. DeNigris a écrit :
>>
>>
>> Stéphane Ducasse wrote:
>>>
>>> rst?
>>> RemoteSmalltalk?
>>>
>>
>> rst = RemoteSmalltalk = SO COOL!!!
>>
>> I easily shared objects from a Pharo 1.1 image with 4 other local images -
>> including a Squeak 4.1 image!
>>
>>
>> For a hoot:
>>
>> 1. In a Pharo 1.1 image with rST installed doit:
>> "Transcript open.
>> RSTSamples serverStartup"
>>
>> 2. In a Squeak 4.1 image with rST installed doit:
>> "RSTBroker
>> startOnPort: self clientPort
>> logging: false.
>>
>> remoteTranscript := ('Transcript@' , self serverBrokerID) asLocalObject.
>> remoteTranscript show: 'everything is ok! (from client side)';
>> cr"
>>
>> 3. Pick up jaw after you see that the squeak image has sent a message to the
>> Pharo image's Transcript, whose contents now appear as 'everything is ok!
>> (from client side)'
>>
>> n.b. According to the docs, in both images, doit: "RSTBroker stop"
>>
>>
>> How to load:
>> I have no write access to rST, so the required packages can be loaded as
>> follows:
>> "Gofer new
>> squeaksource: 'KomHttpServer';
>> package: 'DynamicBindings';
>> load.
>>
>> Gofer new
>> squeaksource: 'KomHttpServer';
>> package: 'KomServices';
>> load.
>>
>> Gofer new
>> squeaksource: 'SPDProjectUpdates';
>> package: 'rST';
>> load."
>>
>> Thanks for the pointer!
>>
>> 1.  This seriously frees me to play with objects in different forks and
>> versions because I know I can beam the live objects to another image
>> whenever I want, and not have them stranded.
>> 2.  This seems like it should be perfect for scripting an image, but what
>> shared object would allow arbitrary code to be run on the server?  I played
>> with Workspace, but got lost down the delegation rabbit hole
>>
>> Sean
>>
>> p.s. I got it loading with minimal changes - just had to fix the underscore
>> assignments, and break the dependency to an old version of KomServices.
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Regards,
>
> Ralph Boland
>
>
> Le 11/08/2010 20:17, Sean P. DeNigris a ?crit :
>>
>>
>> St?phane Ducasse wrote:
>>>
>>> rst?
>>> RemoteSmalltalk?
>>>
>>
>> rst = RemoteSmalltalk = SO COOL!!!
>>
>> I easily shared objects from a Pharo 1.1 image with 4 other local images -
>> including a Squeak 4.1 image!
>>
>>
>> For a hoot:
>>
>> 1. In a Pharo 1.1 image with rST installed doit:
>> "Transcript open.
>> RSTSamples serverStartup"
>>
>> 2. In a Squeak 4.1 image with rST installed doit:
>> "RSTBroker
>>      startOnPort: self clientPort
>>      logging: false.
>>
>> remoteTranscript := ('Transcript@' , self serverBrokerID) asLocalObject.
>> remoteTranscript show: 'everything is ok! (from client side)';
>>      cr"
>>
>> 3. Pick up jaw after you see that the squeak image has sent a message to the
>> Pharo image's Transcript, whose contents now appear as 'everything is ok!
>> (from client side)'
>>
>> n.b. According to the docs, in both images, doit: "RSTBroker stop"
>>
>>
>> How to load:
>> I have no write access to rST, so the required packages can be loaded as
>> follows:
>> "Gofer new
>>      squeaksource: 'KomHttpServer';
>>      package: 'DynamicBindings';
>>      load.
>>
>> Gofer new
>>      squeaksource: 'KomHttpServer';
>>      package: 'KomServices';
>>      load.
>>
>> Gofer new
>>      squeaksource: 'SPDProjectUpdates';
>>      package: 'rST';
>>      load."
>>
>> Thanks for the pointer!
>>
>> 1.  This seriously frees me to play with objects in different forks and
>> versions because I know I can beam the live objects to another image
>> whenever I want, and not have them stranded.
>> 2.  This seems like it should be perfect for scripting an image, but what
>> shared object would allow arbitrary code to be run on the server?  I played
>> with Workspace, but got lost down the delegation rabbit hole
>>
>> Sean
>>
>> p.s. I got it loading with minimal changes - just had to fix the underscore
>> assignments, and break the dependency to an old version of KomServices.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Some time back I posted (to Squeak) the idea of doing development using
> two images.  One image would be your development image, i.e. the image
> you would eventually release as your product.  It would be a
> restricted version of the
> image you have in Squeak/Pharo now.
> The other image would be your software development tool image,
> roughly analogous to what the Eclipse development environment is.
> The advantage of such a set up would be that changes to your development image
> would not blow up your tool image.  You could also leave out anything from your
> development image you didn't actually need in you product such as
> perhaps editors, debuggers, windows, etc. depending upon what software
> your product actually needed.
> I have no plans to actually try this anytime soon.
> But I am wondering:
>
> Would RemoteSmalltalk be helpful in (be a foundation for) creating
> such a utility?

> On 08/11/2010 10:26 AM, Stéphane Ducasse wrote:
>> rst?
>>
>> RemoteSmalltalk?
>
> Yes, and there are multiple other packages too.
>
> A few other things that might be interesting in "inter image communication":
>
> - D-Bus. Bert and the guys made a rather ambitious plugin for libdbus and stuff above it. This is not interesting for Squeak2Squeak, but definitely interesting for cross language stuff.
>
> - Message Queues. There are tons of these today, like RabbitMQ, ActiveMQ etc etc. And there is an AMQP protocol implementation on SS, and yesterday I released a first shot at a STOMP implementation too! These message queues implement publish/subscribe models etc so they are different beasts, but IMHO possible more interesting than "straight RPC".
>
> - If you go for a transport level that is "non Smalltalk", like say a message queue above, then Tirade (also on SS) could work as a fast way to "serialize messages" through such a transport. When I get STOMP finished I will make a simple demo of that.

>
>
> On Sat, Aug 14, 2010 at 4:11 PM, Sean P. DeNigris <[hidden email]> wrote:
>
>
> Noury Bouraqadi-2 wrote:
> >
> > Yes. But, we need an appropriate set of tools. We (Douai's team) developed
> > a few tools a while ago as part of the UbiquiTalk project. We had a
> > remote-workspace working quite fine.
> >
>
> Is this code available?  
>
> I guess
> http://www.squeaksource.com/UbiquiTalk

> Thanks,
> Sean
> --
> View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2325234.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> While some of the suggestions (AMQP, STOMP) were over my head, I'm in the
> process of getting UbiquiTalk to work and already have rST going.
>
> But, for my use case i.e. sending remote commands between (only) two images
> on the same machine, why not just send the commands as strings over a
> socket, and evaluate them with the compiler?  Obviously there's no security,
> but since it's in-house only...  A proof-of-concept is below:
>
> Server image:
> server := Socket newTCP.
> server listenOn: 8081.
> server waitForConnectionFor: 600.
> server sendData: 'Workspace open'
>
> Client image:
> client := Socket newTCP.
> client connectTo: (NetNameResolver localHostAddress) port: 8081.
> Compiler evaluate: client receiveData.
>
> Add a loop and we're all set.
>
> Sean
> --
> View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2400616.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project