Rodrigo Chandía wrote:
Hi Everyone:Do you really need other protocol than HTTP?
Can Servlets be used to handle protocols other than HTTP?
I have to handle a protocol other than HTTP in a request/response fashion so I thought servlets would be a nice way to do it. I guess that an application server can handle connections, threads and such much better than some server app. I could write. The problem is that everything I see in the documentation refers to HttpServlets (except for some passing references to GenericServlet). But that does not tell me how to parse non-HTTP headers and requests.
If servlets are not appropriate, what would be a good way to handle a protocol different to HTTP from an application server?
Thanks in advance.
Regards,
1. You can send Serializable java objects over a HttpConnection/HttpsConnection and read them at the server side using a HttpServlet.
2. You can read Serializable java objects generated by a HttpServlet over a HttpConnection/HttpsConnection;
So why not keep all the benefits that HTTP can give u. You can use the http protocol only as a transport protocol and manage the content as u wish.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
