3 Sep
2010
3 Sep
'10
4:40 p.m.
Right? This means there would be only one WebProcess, which would work as a server for UI client processes which connect to it. I see the benefits of this in an embedded environment where widgets share one common WebProcess and thus this model would use less memory, for example if the WebProcess is used by multiple widgets.
Exactly, that is my idea.
Is there a future plan to support this model too?
At least in my mind it is :) . It would increase the complexity of the framework of course, so it would be important to know other's opinion from the community.