I was try it many years ago with squeak. It was work great. I am sure it should be not difficult to adobt it for latest pharo 08 окт. 2014 г. 1:09 пользователь "Alain Rastoul" <alf.mmm....@gmail.com> написал:
> This is another subject and another functionality I will need too. > > The Rst link is of interest (thank you Denis) , I was thinking > of sending command objects with Fuel as all images will have the same > classes and performance is not very important here. > I was able to load RST in Pharo3, but did not made any test yet. > Does it works with Pharo ? > > @SKrish you are right, but I want to keep as simple as possible at the > beginning and tcpip should fit for a start. > > Cheers, > > Alain > > > Le 07/10/2014 21:40, S Krish a écrit : > >> >> Typical issue in the EJB world : Remote Beans / Local Beans , though on >> inter process it was remote beans with its full stack RMI marshalling / >> unmarshalling. >> >> But can we not exploit shared memory and efficient Event mechanism to >> make the two process coordinate, that should be lot more efficient than >> TCP - IP / but if that performance suffices it would be fine.. >> >> >> >> >> On Tue, Oct 7, 2014 at 4:40 AM, Alain Rastoul >> <alf.mmm....@gmail.com >> <mailto:alf.mmm....@gmail.com>> wrote: >> >> Hi, >> I played a bit with ZnServer and other zinc components and have >> a question I can't answer myself (googling a bit didn't help neither), >> and I'm seeking for advice: does it makes sense to use a >> ZnServer/ZnWebSocket >> as a mechanism to transfer data between two pharo processes - in my >> case 8k ByteArray blocks ? >> Or is it a total non sense ? is it reliable ? >> First tests looks good : 18k blocks / second (145 Mb/s) on a laptop >> core i5 2.6Ghz. >> >> All comments and suggestions welcome >> >> Thanks in advance, >> >> Alain >> >> >> >> > > >
