Re: Persistent Sessions in DB connection for QZDSAOINIT

I think the issue most would have with that is the JDBC connection is being
stored in an HTTP session object which in turn is taking up memory. So as
long as your memory is up to snuff you shouldn't see issue with this.
Anybody please correct me if I am wrong. I would be curious to know if/when
the HTTP sessions objects get paged out of memory to disk. In theory this
would then facilitate your approach quite nicely and only when a stale HTTP
session was being re-activated would a user notice a lag in their session.

If the situation doesn't require that you build for a 1000+ user scenario
then I am also one that takes shortcuts here and there even though they
might not be the purist approach.

Aaron Bartell
http://mowyourlawn.com

On Sun, Oct 26, 2008 at 3:00 PM, Richard Schoen <richard@xxxxxxxxxxx> wrote:

I haven't been following this thread, but I have used a JSP technique
where I have wrapped the JT400 classes in a Java object and then stored
the Java object in the JSP session. I have used the same technique in
.Net as well.

This is a nice way to maintain the same DB connection across page
interactions without incurring startup cost for each page get/post.

This technique may not be viewed by some as the "way to do things".
However it works well and performs very well because you avoid the
connection start penalty for each interaction and the user gets the same
DB and program call connections across pages.

I find there's always a tradeoff between the "way to do things" and what
works and performs well.

Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT