Is it the actual servlet that must be distributed, or is it the
functionality that the servlet implements?
If the latter is the case, maybe you could structure your code so that it
could both be compiled and linked to a servlet, and compiled and linked to
an applet.
-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of
Philippe Bertramo
Sent: Wednesday, September 27, 2000 5:10 PM
To: [EMAIL PROTECTED]
Subject: Servlet engine in a browser
Hello all,
I would like to know if anybody can give some ideas about the follwoing.
I have a servlet application that for some reasons I have to distribute to
some user sites.
I would like to know if there are some applets that can act as servlet
engines so that in the users can run them in their browsers and post / get
data localy using well known HTTP .
Eventually, a java database could be used to store data.
The systems would be synchronized after a while.
All ideas are welcome,
Philippe
= = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Philippe Bertramo
World Customs Organization
Brussels - Belgium
___________________________________________________________________________
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
___________________________________________________________________________
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
