He could also implement the Remote interface and set up RMI communication on a different port than what the HTTP connector runs on - which gives you quite a bit of the protocol set up for free. Any HTTP servlet which implements this interface can also act as a RMI server. IMHO one of the biggest problems with HTTP is that it is a stateless protocol - and passing objects around, and callbacks are clunky at best. For most things though, HTTP does suffice.
If setting up a customized client / server model is really necessary - then an RMI server, or EJB container would seem to be the best choices available at this time. Randy ----- Original Message ----- From: "Milt Epstein" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Thursday, November 14, 2002 11:00 AM Subject: Re: non Http connector > On Thu, 14 Nov 2002, Yves Duhem wrote: > > > Hi, > > I would like to use servlets and tomcat without having to communicate > > via http. > > my request's first line would indicate in some way the target servlet > > and the rest would be the data to transmit to the servlet > > the response would be only the data (no headers). > > (and all this would be used with SSL.) > > > > I would like to know if a connector behaving like this exists somewhere, > > or if i'll have to modify one of the existing connectors (and in that > > case is there any developer documentation about the connector framework?). > > Are you saying that you really don't want to use HTTP (as a protocol), > or just that you want to do this outside the context of a web browser? > Because in the current HTTP framework there's nothing that's stopping > you from using it outside of a web browser. You can, for example, set > up a java application that opens a URLConnection to a Tomcat server. > You can even transfer objects this way (to a certain degree) instead > of just parameters, because you'll have direct control of > reading/writing the I/O streams. > > I'm not really sure what not using HTTP buys you, because then you're > essentially creating your own client/server system and defining your > own protocol, and you have to set everything up. If you use HTTP, you > get a lot essentially "for free" (including parameter passing, > sessions, cookies, ssl, etc.) > > Milt Epstein > Research Programmer > Integration and Software Engineering (ISE) > Campus Information Technologies and Educational Services (CITES) > University of Illinois at Urbana-Champaign (UIUC) > [EMAIL PROTECTED] > > > -- > To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
