Hello Evgeny,
I've updated the benchmark page
(http://www.restlet.org/documentation/1.0/benchmark). Please feel free
to tell us if it answers your questions.
best regards,
Thierry
Hi Evgeny,
Restlet instances are intended to be multi-threaded. Some may require
synchronization of access to member variables, many don't even need
that.
All the state is maintained in the call stack in general, in the
Request and
Response objects passed along the Restlet chain.
However, the Resource class and its subclasses (which are not Restlet
but
similar) are intended to be stateful and dedicated to each request.
See this
part of the tutorial for an illustration:
http://www.restlet.org/documentation/1.0/tutorial#part12
If you still have concerns about general performance, you can check
out this
benchmark: http://www.restlet.org/documentation/1.0/benchmark
Best regards,
Jerome
Thnx a lot for explanation. Seems resources are the more suitable for
my case :)
Btw another issue not related to the questions.
Could you detaliza more in benchmark section what setting of
standalone tomcat/jetty and restler connectors
did u use for benchmark. And also what exact parameters to AB you was
passing.
Sure if this information is not top secret :)
The idea that we are about to start creating some http web service
(not SOAP) and preferrable to show advantages
of restlet-based solution over common tomcat/servlet solution to the
bosses :)
Thnx a lot :)
