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 > > >
