[Glass] forkAt: 25 gem transactions

[James Foster]

Hello Dario,

A Smalltalk Process impacts the scheduling of execution of code but does not impact the object space visible to that code. Each Smalltalk Process instance runs in the same Gem and shares the same object space. Any  changes made to any object in that Gem is visible to all code running in that Gem. Any commit or abort made by any code in that Gem will affect all objects and code in that Gem.

I’m not aware of any design limit on the number of forked processes. 

James

> On Mar 1, 2020, at 6:25 AM, dario.trussardi65 via Glass <glass at lists.gemtalksystems.com> wrote:
> 
> Ciao.
> 
> I started a gem session with topaz.
> 
> After in this session i run some sub processes:		 [...................] forkAt: 25
> 
> 	each of which with a tcp-ip connection read the data from a printer device,
> 
> 		checking that the responses received are consistent with the data sent to the device.
> 
> At this point it is not clear to me how each sub-process manages the transaction with commit or abort.
> 	
> Any sub process is independent from this point of view?
> 
> Any reference, indication?
> 
> Are there any limits to the number of subprocesses (forkAt:) that the system - a gem session can handle?
> 
> Thank you,
> 
> 	Dario
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> https://lists.gemtalksystems.com/mailman/listinfo/glass
>