Why do you want to put the request in the queque? I do something
similar in a messaging application that runs in the background. I
have the message related matters bundled in an interface called
Message that is passed to the multithreaded queque. Is there an
advantage to passing the request to
Santhosh Thomas wrote:
Or, are you trying to run some long-running process and think it would
be better off as it's own thread? If that's the case, you probably want
to look into some sort of queueing mechanism with either status polling
or some sort of callback when the task is complete.
Has there any way to implement asynchronous request/response using
servlets?
Not directly. What you can do though is submit the request from the
browser, put some operation in a queue and return immediately with a
page that will call another servlet (or the same one, either way) to
poll for
Hi
I know this is a basic question. I am passing the request and response object
to another thread from the doGet() and after that the Get method returns. So
that the processing is done in the thread and response to client will be
flushed later. But by that time the servlet method would
Couple of things...
No, I don't believe you can do anything with request/response after you
exit doGet(). Well, let me amend that... you MIGHT be able to get away
with it, but I wouldn't expect it to work all the time. What I mean is,
once your servlet is done it's work, the container takes
Or, are you trying to run some long-running process and think it would
be better off as it's own thread? If that's the case, you probably want
to look into some sort of queueing mechanism with either status polling
or some sort of callback when the task is complete. Again, more details
would
