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 > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Evgeny Shepelyuk > Envoyé : mardi 8 mai 2007 17:36 > À : [email protected] > Objet : Re: Restlet lifecycle question > > Jerome Louvel <contact <at> noelios.com> writes: > > > > > > > Hi Evgeny, > > > > In this case and for all other Restlet instances, the same > instance is > > reused across requests and even multi-threaded. No worry > about performance. > > > > Best regards, > > Jerome > > Hello, > So can you describe in which cases i´ll get different > instances of restlet(or > sublclasses) serving incomng requests. > First i really worry about perfomance in this case :) > Second can be synchronization issues if i use some temporary > instance variables. > > Thnx >
