Hi, I'm currently implementing a Java client for an existing RESTful webservice using Restlet.
The client library will be used as the fundament for a web application, thus it will have to handle many concurrent requests. So I'm wondering how to setup a highly scalable Restlet client. So far, I've chosen HttpClient as underlying client and increased the number of max connections per host. Now I've seen a note in the docs, that ClientResources can't be shared between thread. When each request will be dispatched to a new ClientResource, I see new http client instances spawning all the time instead of using connections in the existing pool and I lose the advantages of connection pooling and persistent connections. So how can I now use client-side Restlet without going too much into the lower stuff. The client resource doc states that a client should be issued directly in such scenarios. For me, this would make the usage of Restlet rather obsolete, when I can't use the highly abstracted ClientResources and mappings. Thanks in advance for you advices and insights! ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2635381
