Jeff, i fully agree with you that this would be the right direction and a win-win situation for both communities. This would be however not only a question of "turning the build setup", but a substantial amount of rewriting of e.g. the i/o and threading layers.
A few years ago i have looked a little into replacing aolserver's threading layer by libthread. That would give the benefit to have all threads sitting in an event loop, making thread reloading etc. much easier (connection and scheduled threads). I've failed to convince Zoran to move this way (due to the required amount of work). -gustaf neumann On 29.09.12 02:52, Jeff Hobbs wrote: > It is likely quite possible to turn things around and have AOLServer be > a set of extensions that load into a standard tclsh. The state of > extensions is pretty open, and again if more of the Tcl standard code > can be leveraged (socket handling, threading, etc.), this would be a > good thing. After all, a lot of that was originally influenced by > AOLServer code. > > I think this would be a win for portability as well as ease of use, but > it may be a larger task to turn the build setup on it's head than anyone > wants to undertake for a minor version update. > > Jeff > ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
