I firmly beleive that it makes much more sense to make Pike "pure" (ie. no global variables) and then instansiate more than one interpreter in the same process, each with it's own interpreter lock and thread(s).
If one does that, one could create some Pike abstraction for passing data between the interpreters, which could potentially be more efficient than ordinary interprocess communication.
Indeed, that would be very nice. In fact, the abstraction layer should probably be created first, as it would also be very very useful for passing data between Pike processes. An optimized version could then be created later for in-process communication.
A "pure" pike is also good for anyone who wants to embed pike into other programs.
Absolutely, it would make mod_pike really really easy...
/ Fredrik (Naranek) Hubinette (Real Build Master)
Previous text:
2004-02-01 21:08: Subject: Re: Default backend and thread backends?
I firmly beleive that it makes much more sense to make Pike "pure" (ie. no global variables) and then instansiate more than one interpreter in the same process, each with it's own interpreter lock and thread(s).
If one does that, one could create some Pike abstraction for passing data between the interpreters, which could potentially be more efficient than ordinary interprocess communication.
A "pure" pike is also good for anyone who wants to embed pike into other programs.
/ Niels Möller (vässar rödpennan)