> > 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 have the following configuration working: 1) libevent (libevhtp) at the front 2) Tntnet components run in the back, called via reverse-proxy 3) Tntnet components called directly from under the libevhtp callback The (2) have to happen first in order to get hold of a pointer to the Tntnet component. When (2) happens, the Tntnet component will wrap itself into libevhtp: <%init> libevhtpCallback (this); </%init> Calling Tntnet component directly (3) is ten times faster than calling it via reverse-proxy (2). Here's some code: https://gist.github.com/4248402 Tommi, could you make it easier to get the component from the Tntnet? I haven't found a way to get a hold of it except running it or other component. Perhaps a public `fetchComp(const Compident& ci)` in framework/common/tnt/tntnet.h? ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
