I think it's quite a problem to leave http protocol behind but use servlet further. The servlet container needs url information from the "GET" or "POST" header to find the corresdonding servlet. So the request is restricted to obey http request rules. I think your question is about a none "html" server, isn't it? One example application for using a servlet serving XML output is a Flash- or Applet-client.
Peter souravm wrote: > Hi All, > > Can anyone tell me what advantage one can get in implementing a non-http > server using Servlet instad of implementing the same using simple Java > class. > > Regards, > Sourav > > ___________________________________________________________________________ > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff SERVLET-INTEREST". > > Archives: http://archives.java.sun.com/archives/servlet-interest.html > Resources: http://java.sun.com/products/servlet/external-resources.html > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html -- Peter Huber (IT Consultant) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Gauss Interprise Consulting AG Gesch�ftsstelle M�nchen Witneystr.1 D-82008 Unterhaching Telefon: +49-89-66561 - 128 Fax: +49-89-66561 - 199 e-mail: mailto:[EMAIL PROTECTED] Germany Web: http://www.gi-consulting.de ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
