Barney Boisvert wrote: > I share the same assumptions, seems foolhardy to do it differently, both for > performance and logistical reasons.
That is debatable. If the pageflow is something like <small query>, <long processing>, <small query> it might be better for performance to release the connection back to the pool in the mean time. And to handle all the logical issues we have cftransaction. > Anyone from the CF team still around to comment? It's not even 4:30 yet. ;) Why not just test it yourself? Just run the following template from multiple browser Windows simultaneously: <cfquery name="test" ...> SELECT CURRENT_TIMESTAMP AS runtime </cfquery> <cfoutput>#test.runtime#</cfoutput> <cflock name="wait" type="readonly" timeout="2"> <cflock name="wait" type="exclusive" timeout="10" throwontimeout="no"> </cflock> </cflock> <cfquery name="test" ...> SELECT CURRENT_TIMESTAMP AS runtime </cfquery> <cfoutput>#test.runtime#</cfoutput> Then dig out a version of CF where the datasource connection limit works, set it to 1 simultaneous connection and repeat the experiment. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
