Hello: I have written an RMI server application to be accessed from RMI applets inside our firewall and outside it. The server application and the client applets worked together well but we ran into performance problems due to HTTP tunneling and other things. I have read in this mailing list that due to firewall problems, people implement RMI Servlets. However my little investigation (without writing any code) of RMI Servlets shows that they do not necessarily solve the problems described above. Mainly this is because RMI Servlets are just like my RMI Server application with the added capability of listening to an HTTP port. I am NOT intersted in HTTP access! My client code is an RMI applet. My question is: what does it buy me to use an RMI Servlet vs. an RMI Server? Thanks for your help... Regards, Khaled ___________________________________________________________________________ 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
