Tommi Mäkitalo <tommi@...> writes: ...
> Am 19.07.2012 09:26, schrieb ArtemGr: > > Is there a way to extend the TCP/IP socket lifetime past the > > Worker::processRequest in order to send the response later > > while not keeping the Tntnet thread pinned? ... > I feel, that it is time to make a larger change. I have already thought > a little about replacing the whole event handling with the cxxtools > event handling, so that tntnet can run in the same event loop like the > rpc servers in cxxtools. But this is really a larger project, which > needs some time. > > The goal is to keep tntnet source compatible, so that no user changes > are needed. Meanwhile I ran into problems with Tntnet proxy because it is thread-bound (and there's no way to suspend the request while the http client is working) and ate the Tntnet thread pool easily. So I ended up moving libevent to the front and putting Tntnet behind. (Here is my libevent proxy, btw: https://gist.github.com/3911541). ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
