I am building an applet-servlet-database application, and I have a design
question.
The applet collects info, builds a query object, sends it to the servlet
(http serialized object), which sends it to the db-server (rmi) to get the
result set. The result set is returned to the servlet (rmi callback), which
sends to the applet (http serialized object), and the applet puts the result
set in a JTable. I want to keep the applet-servlet link simple so I don't
get into any firewall issues. I put the applet-servlet communication
activity in a separate thread so the applet can do other things while
waiting for the response from the db.
My questions are:
1. Should I build a query object, or just send the query as strings in GET?
There are only 5 to 20 parameters in a query.
2. Can I send the JDBC result set back to the applet as a serialized object,
or is it better to "unpack" it at the servlet and send it as my own result
set object?
3. Do I need a connection pool at the servlet? I expect between 2 and 15
simultaneous accesses to the db from different applets.
Any other observations about the architecture would be greatly appreciated!!
Mark
****************************************************
Phillips Marketing, Inc.
Internet marketing, e-commerce, groupware, and new ventures
602 945-0798
Fax 945-9197
[EMAIL PROTECTED]
http://members.home.net/phillipsm
___________________________________________________________________________
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
