PS I don't think there is anything in the Servlet spec about "not" creating threads.
On 7 March[masked]:01, Jim Collins <[address removed]>
What is so wrong with introducing concurrency in a web app? If the Servlet request has to make some potentially long running call then it makes sense to have a policy for dealing with this so subsequent requests do not block.
On 7 March[masked]:55, Ged Byrne <[address removed]>
You open yourself to a whole world of pain once you introduce concurrency. If you can avoid it then you should.
If there is an unavoidable need for concurrency then you might want to consider using Camel. Then you are managing queues rather than threads, which is much easier.
On Wednesday, 6 March 2013, Jon Hatfield wrote:
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Ged Byrne ([address removed]) from LJC - London Java Community.
To learn more about Ged Byrne, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]