Sumit, The Application can declare which client and server protocols it supports/needs via the Application.getConnectorService() and related methods in ConnectorService.
This needs a bit of refactoring though. I'd like to provide those methods for beta 21: - getClientProtocols - getServerProtocols instead of the current four: - getOptionalClientProtocols - getOptionalServerProtocols - getRequiredClientProtocols - getRequiredServerProtocols When an Application is started by the container, I will also make sure that the necessary connectors are available, otherwise log an error. Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Sumit Lohia > Envoyé : mardi 14 novembre 2006 19:37 > À : [email protected] > Objet : Re: Client connectors and Applications > > Jerome Louvel <contact <at> noelios.com> writes: > > > > > > > Hi Sumit, > > > > Container create/manage the connectors because they > can/should be shared > > between multiple applications (think about virtual hosting multiple > > applications on the same HTTP 80 port). For client > connectors we want to be > > able to implement connection pooling, etc. > > > > From inside an application you can easily use the > container's connector via > > the Restlet's Context and its "getClient()" method (to be renamed > > getDispatcher() in beta 21). > > > > Best regards, > > Jerome > > > > Jerome, > > So the Application cannot request the Container to add > support for a new > Protocol. Is that correct? If the Container already supports > a Protocol, the > application can use it via the getDispatcher(), but it cannot > request the > Container to add support for that protocol. > > Just wanted to clarify my thoughts. > > Thanks. > > Sumit > >
