Am 02.10.2012 17:52, schrieb ArtemGr: > Tommi Mäkitalo <tommi@...> writes: >> Am 01.10.2012 20:42, schrieb ArtemGr: >>> I'd think you need to instantiate it in the Tntnet components, >> Right. request-scope is fine also. > What happens if the request is finished in the user's scope > but not finished in the Tntnet's scope? > E.g. the data is generated and returned to Tntnet's reply.out(), > but the client is still downloading it. The request scope is released after the reply is fully sent to the client. Or at least after the data is passed to the kernel and hence out of scope of the process. So no problem here. And indeed a good argument not to put the class on the stack but in the request scope.
Tommi ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
