hi all!

I am currently planning similar things; and actually am open
to any suggestions:

 > From: Ted Neward <[EMAIL PROTECTED]>
 ...
 > synchronization, or else open multiple Connections, one per user. When you
 > consider that ODBC does some connection pooling on its own, anyway, this may
 > be less of a cost than you think.
 ...
 > > From: Nitin Kulkarni <[EMAIL PROTECTED]>
 > >I need some help regarding multiuser programming using Servlet. We have
 > >developed an application which runs as follows
 > >
 > >HTML ----> Servlet----->
 > >                                      Database(MS Access)
 > >HTML  <---Servlet<-----

I my version, the DB just happens to be Berkeley DB; and my
plan is to layout things like this:

browser <-(1)-> servelet <-(2)-> db access processes (to be process pooled).

and to do SunRPC at connection (2) to let each of the db
processes on the right act like a set of process pooled RPC
servers.

while this seem to work for now, I'm still wondering if things
might be much easier (or cleaner) if I've changed the protocol
at (2) to be based on Java RMI (currently both end of (2) is
written in C, requiring JNI on the Java side -- I've never used
RMI so far). or slightly stepping back, to rewrite the stub on
these RPC end-points to be written in Java (but I'm rather
hesitant to purchase commercial Java rpcgen products).

thanks much,
kenji

___________________________________________________________________________
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

Reply via email to