Hi RK, If your application is client-side only, you can manually instantiate a client connector and reuse it for all ClientResource instances:
Client myClient = new Client(Protocol.HTTP); ClientResource cr1 = ... cr1.setNext(myClient); ClientResource cr2 = ... cr2.setNext(myClient); Otherwise, you can also reuse it implicitely by creating new ClientResource from an original one, using the getChild(...) method. A final possibility is to use a parent Component with a proper Client registered and a contained Application. Best regards, Jerome -- Restlet ~ Founder and Technical Lead ~ http://www.restlet.org Noelios Technologies ~ http://www.noelios.com -----Message d'origine----- De : [email protected] [mailto:[email protected]] Envoyé : lundi 27 décembre 2010 15:52 À : [email protected] Objet : ClientResource Performance Are there any benchmarks in terms of performance when communicating between client and server running on different machines in Restlet Framework? Every ClientResource call seems to open a HttpConnector and then close it based on my release() call on the ClientResource. I find the overall performance of communication between my client and server seems to be somewhat slow. Not sure if I am missing something in terms of optimal way of using Restlet framework or I have someother issue outside HTTP connecting slowing things down. I am exchanging ObjectRepresentations between my client and server. My server does database access through hibernate. Can someone share any tidbits interms of performance of Restlet framework? Regards, RK. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2693976 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2694525
