On Wed, 22 Nov 2000, Myriam Abramson wrote:
> Hi!
>
> Is there a difference in the performance of a servlet using http
> requests vs. a server-side application using tcp/ip sockets?
Not a real specific and/or complete answer (but then neither is your
question :-), but I'd suspect that there would be, with the sockets
winning. It makes sense, since with sockets, you'd have all the
control, and could fine-tune things for performance -- e.g. could use
your own communcation protocol, could do things at a lower level,
could keep the sockets open, etc. With servlets, you're stuck using
http -- e.g. the request/response mechanism, you'd have to "translate"
the data coming in as parameters to the format you need (although if
the request is coming from an applet, you can avoid using parameters,
but you may have to worry about managing sessions yourself).
Of course, there are some advantages of servlets/http as well.
Perhaps most importantly, secure/proxy sites may not allow traffic on
an arbitrary port, while most allow port 80/http traffic. Also, using
http means you're going with a standard, well-accepted protocol.
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
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
