On Feb 4, 2008 7:47 PM, Paul McNett <[EMAIL PROTECTED]> wrote: > Alan Bourke wrote: > > > MB Software Solutions wrote: > >> Because I don't like the idea of open/close/open/close/open/close for > >> every stinking SQL. > > Doesn't it have some sort of connection caching/pooling scheme like SQL > > Server, where even though you might tell it to close a connection or it > > might time out, it doesn't actually close it? > > Now *that* sounds like a MS move for sure! The developer says "close the > connection" and the server, behind the scenes, keeps it open for you. > ---------------------------------------------------------------------------------------------------------------
It is the most costly thing to do is to get a connection. In the end your not getting ANY DATA, just a token. I wonder if we can credit Al gore with inventing this idea as well? Bad Steve! Every server needs to cache connections to make speed blazing. The Close statement is kept in the cache but it is used as a marker to CONSIDER terminating this token and not a stop this milli second. -- Stephen Russell Sr. Production Systems Programmer Mimeo.com Memphis TN 901.246-0159 --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
