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 this week at my "real" job, then turn my attention to cleaning and posting this =)
- R On Wed, Feb 27, 2008 at 9:09 AM, Tim Peierls <[EMAIL PROTECTED]> wrote: > 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 is a good summary of the issues. > > --tim > > > On Wed, Feb 27, 2008 at 8:47 AM, code dude <[EMAIL PROTECTED]> wrote: > > > 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 use thread pools is to submit tasks from the response > > > handling thread and block until the tasks. In addition, Request and > > > Response > > > objects are not thread-safe, so you have to manage access to them very > > > carefully. > > > > > > Rob Heittman wrote an excellent summary of several overlapping issues > > > that touch on asynchronous request handling: > > > > > > http://www.mail-archive.com/[email protected]/msg03876.html > > > > > > And issue 143 has lots of pointers to discussions: > > > > > > http://restlet.tigris.org/issues/show_bug.cgi?id=143 > > > > > > --tim > > > > > > On Wed, Feb 27, 2008 at 2:53 AM, code dude <[EMAIL PROTECTED]> wrote: > > > > > > > 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 ( response.setEntity) user get no outcome in browser or http > > > > client ...............I dont know why .....can anybody pl suggest me > > > > why its > > > > happening ....orther wise it works perfectly > > > > > > > > > > > > Regards, > > > > cd > > > > > > > > > > > > > > > > > >
