Obi a écrit :
Hi Nicolas,
Yes I've been using Tora's redirect until now but as I suppose it just
sets an function to be executed for those neko.Lib.print &
neko.Lib.printLn methods, where in multi-threaded env. if those print
methods are invoked -> the redirect won't work as expected.
redirect will redirect all prints being done by the VM for the current
thread, since there is one-VM-per-thread. So unless your service create
threads that does some print (which I would advise against) it should be
fine since all the threads are created by your server which can capture
prints and redirect them they way it wants.
There is no need for the web app implementation to maintain and create
Threads because of the fact that uberTora handles them and just
redirects the client requests in thread-safe way - isolating the
client request's data per every redirect, so the server can
handle/serve other request->responses at the same time.
This is also the case for "classic" Tora, I'm not sure that I understand
what uberTora does differently ;)
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
