Re: Response Object Threadpool issue : Response Object stops working inside a thread

Hi All, Do you need syschoronize Responce object when used inside a thread .its just stops working inside a thread (threadpool) Am I missing something I am stuck at this problem for last 3-4 days , any help will me much appreciated Rgds, cd On 2/27/08, code dude [EMAIL PROTECTED] wrote:

Re: Response Object Threadpool issue

On Wed, Feb 27, 2008 at 8:36 AM, Tim Peierls [EMAIL PROTECTED] wrote: Currently RESTlet doesn't support asynchronous handling of requests, so the only way to use thread pools is to submit tasks from the response handling thread and block until the tasks. That should have read ... until the

Re: Response Object Threadpool issue

Thanks Tim ...What About servlet response in Jetty or Tomcat ...do they support asynchronous handling of requests?? , can this be overcome thru callbacks ?? On 2/27/08, Tim Peierls [EMAIL PROTECTED] wrote: Currently RESTlet doesn't support asynchronous handling of requests, so the only way to

Re: Response Object Threadpool issue

The servlet model is inherently thread-per-request. The only way to use multiple threads when handling a request is to block the handling thread until all other tasks related to the request are complete. You have to go beyond the servlet model to break out of this constraint. Rob Heittman's post

Re: Response Object Threadpool issue

FYI, somewhere in next week I hope to be landing the working GWT code that experiments with the async-style handle. Jerome's created a spot for it out of the normal modular build, so the experimental code isn't confused with actual Restlet internals. I just have to finish murderous deliverables

Response Object Threadpool issue

Hi All, We have recently migrated from SOAP webservices to RESTlet based Rest architecture , where we get parameters via post , make api calls/ do processing in threadpool and return/write back to response object .but when i write results to send object in thread pool thread (