Code Forums - View Single Post

sde · 05-18-2004, 07:10 AM

hi bel and thanks for the code , ..

question: is there something wrong with using javax.sql.PooledConnection ?

correct me if i'm wrong, but it looks like your code would pool a connection when the web page is executing, .. and the connection would probably close before the page was requested again.

i need the connection to stay open for let's say 60 seconds. any other pages requested by the same user ( or different users ) will use this one open connection.

does your example do that? i've been working with the PooledConnection object and it seems to enhance performance a bit, but i'm not sure if it keeps the connection open between pages.

if my database manager object goes out of scope ( when the web page is completed ) then i'm not sure how the next request knows that a connection already exists.

i'm not being very clear because i'm not sure what to ask, .. but do you have any thoughts on this?

05-18-2004, 07:10 AM	#7 (permalink)
sde Moderator Join Date: May 2002 Location: us.ca Posts: 4,503	hi bel and thanks for the code , .. question: is there something wrong with using javax.sql.PooledConnection ? correct me if i'm wrong, but it looks like your code would pool a connection when the web page is executing, .. and the connection would probably close before the page was requested again. i need the connection to stay open for let's say 60 seconds. any other pages requested by the same user ( or different users ) will use this one open connection. does your example do that? i've been working with the PooledConnection object and it seems to enhance performance a bit, but i'm not sure if it keeps the connection open between pages. if my database manager object goes out of scope ( when the web page is completed ) then i'm not sure how the next request knows that a connection already exists. i'm not being very clear because i'm not sure what to ask, .. but do you have any thoughts on this? __________________ Mike