Hey!
I have two questions about the above Subject, one concerning
servlets (on-topic) and one concerning applets (off-topic).
Architecture presently:
Database, web server and servlet engine is on one Intel/NT box.
All servlet access to the database is with direct connections like:
"jdbc:db2://serverName:port/databaseName",
where serverName
is the same for the webserver and the database connection.
Architecture proposed:
But, when I try to move the database to a different box, say
"jdbc:db2://serverName_on_a_different_box:port/databaseName",
I will get a Security violation warning that I am trying to access
another
machine. Will someone help with some ideas.
Applets have the same problem and maybe even a more difficult one to
solve. All of the applets access the database same as above.
Because the applet is loaded into the web browser, I think I
am at the mercy of the web browser security. What to do?
Is there a solution that will work for both servlets and applets?
Is seems only natural that this is the next progression from getting
servlets running on one box with small amounts of data residing in
a DB to the day when the DB data gets to be too big. In
that case, It doesn't make good sense to have the DB and web stuff
on the same box, IMO. I think servlets are in a new phase now.
They have proven to be a viable solution to the delivering the
Business model.
If any one knows how to do this, I think it has to be someone on this
E-list. :>)
Thank you.
Danny Rubis
___________________________________________________________________________
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
