Do you plan to consume method's response in the same request? If not, some sort of MQ/JMS may be an option--just put your message there and return. The message itself will be processed in separate thread with MQ handler (Message-Driven Bean in case of Java EE).
On Wed, Jun 13, 2012 at 4:56 PM, Angelo C. <angelochen...@gmail.com> wrote: > hi, > > Got this situation, for every request, I need to call a function of a > service, if I understand it, this is a 'blocking' code, the flow will > continue only when the function returns, solution that I can think of is, > create a thread, and let it run, but considering so many requests can > happen > in the same time, this might be quite costly, any better suggestion? > Thanks, > > Angelo > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/non-blocking-code-in-T5-tp5713836.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Dmitry Gusev AnjLab Team http://anjlab.com
