Hi,
I think Grizzly continuation of/and comet should do what you need.
Unfortunately I don't have much experience with that :(
We can wait until Jean-Francois will wake up in Canada and describe
how it could be done.
Thanks,
WBR,
Alexey.
On May 22, 2008, at 6:41 , sumitsureka wrote:
>
> Hi Alexey,
>
> You are right on this:
>
> [As I understand you have scenario, where request processing takes a
> long time (some complex computation, big database requests etc) and
> you don't want processing thread block until the request will be
> processed... Is this correct?]
>
> Currently, my program get the control in the method service(Request
> request,
> Response response), say this is Thread-1, from where I pass the
> request to
> the next thread say Thread-2, which does the required processing.
> Meanwhile,
> the Thread-1 (service thread) is waiting for the request to get
> processed
> which in general may take long time.
>
> Due to high latency, I am unable to start the processing of the next
> request, which I do not want. I want something like that the
> Thread-1 should
> not wait for the response and should start accepting other requests.
> When
> Thread-2 completes processing the requests, then in that case Thread-2
> itseld should be able to provide the response through the same
> connection to
> the client.
>
> I hope, I am able to explain the scenario. Please let me know if
> there is
> anything that I have missed out.
>
> Regards,
> Sumit
> --
> View this message in context: http://www.nabble.com/Grizzly-and-Axis2-tp17303209p17397255.html
> Sent from the Grizzly - Development mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>