> Hi Dionisios, > > What you observe is the expected performance of the *internal* HTTP > connector, built-in the org.restlet.jar. This connector has been redesigned > for 2.0 to support advanced HTTP features such as provisional responses, > pipelining, asynchronous handling and future enhancements such as unified > thread pool, IO-level firewall, etc.
I believe that approximately 200ms response time is largely due to Nagle's algorithm. Substituting the Apache HttpClient (either direct or wrapped by ClientResource) cuts the time by half to around 100ms. Could you consider disabling Nagle's algorithm on both server and client sockets used by the internal connectors? Regards, Mark Thornton mthornton at optrak dot co dot uk ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2676245
