Closed guenterh closed 10 years ago
We had the problem with native HTTP connectors delivered with the Restlet framework. It happens that KVK couldn't test the new service because response times were really poor. It was reported sometimes around 60 seconds. (they used a TCL client
Same issue appears while using the urllib2 module from Python or the simple @file_get_contents method with a PHP client. I didn't stumble upon this problem with a Java client using e.g. the URL type.
With the old python module (there seems to be better designed modules for REST requests) as well as the PHP @file_get_contents method and obviously a TCL HTTP client the Restlet server (using native HTTP connectors) came in trouble with synchronization of threads and blocked the response for a long time so clients got this terrible response times.
Using the http Connectors of Servlet containers in conjunction with the RestletServlet extension seems to solve the problem.
Now we have the possibility to deploy the service within a Servlet container for production but could use the Restlet Application as a stand alone component for simple development
Nice!
Günter
more testing for stability is necessary!
decide about deployment (Tomcat or Java virtual machine for restlet process on each host)