I know there are many ways of persisting data throughout a web application.
I am looking for the best match for mine.
Pros, cons, howto's, general opinions are welcome.
The first large scale web application I wrote was in ASP land.
We wrote our DLL in VB, used (abused) the session object for
persisting the collections of data. Life was good.
Then the use of the session object got out of hand. (To easy to abuse I suppose!)
And our performance went down the drink, it became unstable, and I don't even want
to talk about threading issues. What a nightmare!
Now I am on to JSP, Servlets, beans, WebSphere.
(Where I wanted to go in the first place. But that is in house rant that we won't go
into! No flaming wars please!)
The application will be of order entry flavor, tracking, admin, catalog, shopping
carts, etc.
So the collections could get fairly large and complex.
Session scope Beans?
Collections of some sort? i.e. Vectors (is this a simple name/value pair?)
Session object?
Data base? Last resort for performance issues.
Really looking articles, example / sample code of a large scale application style.
Thanks!
___________________________________________________________________________
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
