multithreading - Good or bad idea: Multiple threads in a multi-user servlet-based web application with Java -


i building java-servlet-based web application should offer service quite lot of users (don't ask me how "a lot" :-) - don't know yet).

however, while application being used, there might occur long-taking processing on serverside. in order avoid bad ui responsiveness, decided move these processing operations own threads. means once user logged in, can happen 1-10 threads run in background (per user!).

i once heard using multiple threads in web application "bad idea".

is true , if yes: why?

update: forgot mention application heavily relies on ajax calls. every user action causes new ajax call. so, when main servlet thread busy, ajax call takes long process. that's why want use multiple threads.

it bad idea manually create threads yourself. has been discussed lot here in so. see this question example.

another question discusses alternative solutions.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -