interesting. Its something that sounds easy, but could be quite 'hard' as it could leave a lot of things in a undeterminate state.
What could hold things up? Surely if its a CFHTTP you can add a timeout, or a database, then you set the maximum time a query has to run before the pool removes it. So taking that out of the equation, help me understand what other areas you would want to catch for? Give me an example please? Alan Holden wrote: > I would just like to add my vote of importance to this point: > > Being able to place something like <cfsetting requesttimeout="3600"> > at the top of just one CF page, without casting some global > requirement outside OpenBD, that allows any one of my CF pages > to tie up a process for this long as well. > > My apologies if I misinterpreted this thread. --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
