Sang did something similar a while ago too.
https://github.com/lxsang/SystemProcess 
<https://github.com/lxsang/SystemProcess>

It allows an image to launch workers. One thing interesting is that they share 
virtual memory, so they can exchange data during the execution

Noury

> On 27 Jun 2019, at 06:26, Alexandre Bergel via Pharo-users 
> <pharo-users@lists.pharo.org> wrote:
> 
> 
> From: Alexandre Bergel <alexandre.ber...@me.com>
> Subject: Re: [Pharo-users] Anything on Pharo that would be like Opentalk on 
> VW?
> Date: 27 June 2019 at 06:26:32 CEST
> To: Norbert Hartl <norb...@hartl.name>
> Cc: Any question about pharo is welcome <pharo-users@lists.pharo.org>
> 
> 
> I do not know what is ImageWorker, but DMirror is a simple and efficient way 
> to distribute a computation on single CPU.
> 
> Alexandre
> 
>> On Jun 25, 2019, at 3:05 PM, Norbert Hartl <norb...@hartl.name 
>> <mailto:norb...@hartl.name>> wrote:
>> 
>> 
>> 
>> Am 25.06.2019 um 20:44 schrieb Alexandre Bergel <alexandre.ber...@me.com 
>> <mailto:alexandre.ber...@me.com>>:
>> 
>>> Hi Jerry,
>>> 
>>> We have worked on bridging Pharo with Python. It works remarkably well. 
>>> Here is the website: https://objectprofile.github.io/PythonBridge/ 
>>> <https://objectprofile.github.io/PythonBridge/>
>>> We have also worked on a simple mechanism to distribute computation across 
>>> multiple Pharo images. Here is the website: 
>>> https://github.com/ObjectProfile/DMirror 
>>> <https://github.com/ObjectProfile/DMirror>
>>> 
>> Nice! How does the DMirror relate to the ImageWorker?  
>> https://github.com/pharo-contributions/ImageWorker 
>> <https://github.com/pharo-contributions/ImageWorker>
>> 
>> Norbert
>>> Cheers,
>>> Alexandre
>>> 
>>>> On Jun 23, 2019, at 11:09 PM, Jerry Kott <jk...@image-ware.com 
>>>> <mailto:jk...@image-ware.com>> wrote:
>>>> 
>>>> I am looking at some interprocess communication with Pharo. VW has 
>>>> Opentalk, VASt has Sst (I think, haven’t looked in a while). Does anything 
>>>> similar exist for Pharo?
>>>> 
>>>> Jerry Kott
>>>> This message has been digitally signed. 
>>>> PGP Fingerprint:
>>>> A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5
>>>> 
>>>> 
>>>> 
>>> 
> 
> 
> 

Reply via email to