Hi, Tommi! 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?
If I'm not mistaken, the socket which is left after the HttpReply::setDirectMode has a chance of not being destructed immediately because Tntnet would wait for further KeepAlive requests, but that doesn't seem reliable. Would it be hard to implement a method in Tntnet which takes the socket out of the Tntnet loop? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
