I am not very sure I understand. The Restlet client by default uses apache HttpClient. There are a bunch of configurable settings that can be provided to Restlet which trickle down to the commons HttpClient like maxConnectionsPerHost or connectionManagerTimeout etc. The maxConnectionsPerHost is used to control the maximum number of simultaneous Http Connections that will be opened and pooled. If the Restlet Client was to not intended to service multiple thread at the same time, then these parameters and settings become superflous IMO.
Thanks, Sanjay ---------------------------------------- > Date: Thu, 16 Oct 2008 09:28:57 +0200 > From: [EMAIL PROTECTED] > To: [email protected] > Subject: RE: Assistance and Question > > Hi, > >> That said, the direction of preference seems to point to using a >> single instance of Restlet's Client class and setting the "maxConnectio >> nsPerHost" to some >> appropriate value. One concern that I have is whether Restlet's >> Client is designed to be thread safe so that multiple threads can >> utilize the same instance? >> In other words, is singleton usage the recommended pattern for using >> the client? > > I think singelton usage is not useful, because you could set different > properties or something like this, if I remember right? > > best regards > Stephan > _____________________________________________________________________ > Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 > _________________________________________________________________ When your life is on the go—take your life with you. http://clk.atdmt.com/MRT/go/115298558/direct/01/
