Re: ExclusiveLock
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31839
interpreted = N
texte = >>What if [EXCLUSIVELOCK] locks some db's, but fails to unlock them for >>some reason? Wouldn't that prevent all other requests to the same >>db's from executing until webcatalog is shut down and restarted? > >for some reason would be considered a bug, so unless that actually >happens during beta, you shouldn't need to worry about it.This makes no sense to me.What if we don't happen to get lucky enough to see this happen during the beta? Then what? It brings our sites down later -- without warning? That's no way for us to have to deal with this possibility ...I am simply asking you to code the software so this will *never* happen -- bug or not. To do this we should have a timeout we can set, either in the prefs or as an optional parameter to the [exclusivelock] context -- to terminate an exclusivelock after a set period of time. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
>>What if [exclusivelock] locks some db's, but fails to unlock them for >>some reason? Wouldn't that prevent all other requests to the same >>db's from executing until webcatalog is shut down and restarted? > >for some reason would be considered a bug, so unless that actually >happens during beta, you shouldn't need to worry about it.This makes no sense to me.What if we don't happen to get lucky enough to see this happen during the beta? Then what? It brings our sites down later -- without warning? That's no way for us to have to deal with this possibility ...I am simply asking you to code the software so this will *never* happen -- bug or not. To do this we should have a timeout we can set, either in the prefs or as an optional parameter to the [exclusivelock] context -- to terminate an exclusivelock after a set period of time. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Custom WebCat Prefs ... (1997)
WebCat b13 CGI -shownext- (1997)
WebCatalog dying in WebTen (1998)
iTools5.0014 and up + WebCat = DownServer (2000)
CommitDatabase vs. CloseDatabase (2001)
oops private message leaked into talk list (1997)
Cart ID (1999)
Macos8.6 to X migration problems (2000)
[WebDNA] why is this cookie being set to expire at end of browser session? (2009)
Buggy Code (1998)
RequiredFields notes ... (1997)
Color (1997)
WC2b15 File Corruption (1997)
MacAuthorize Hub/Client and program linking (1997)
redirect with frames (1997)
Two submit buttons ? (1997)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
shipcost (1997)
[numFound] inside [showIf]? (2000)
4.5 License (2005)