Re: [WebDNA] Timer

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 101737
interpreted = N
texte = Jason Adams wrote: > Hi Chris, > > I do not mean to offend but I find no reports of "trigger bugs fixed" > in the mail list archive. Instead I see several reports of failed > triggers over a long time, including this post made just days ago: > >>> WebDNA Version 6 >>> In the ISP Sandbox settings there are "Sandbox Options" >>> for Emailer and Triggers. >> These are buggy in 6.0a so keep them checked on that >> version. They should be fixed in the CICADA (6.1.x build) >> but, I have yet to test the fix thoroughly. > > In this post Mr. Brooke seems to feel the bug may not yet be fixed > even in the new version, thus I hesitate to trust triggers given the > fact that timed event actions are mission critical for us. > > On 1/3/09, christophe.billiottet@webdna.us > wrote: >> A way to do that would be to add a "timestamp" to a small "witness >> database" with only one record, any time the main database or the file >> is updated (you must add a small [Replace] command to update the last >> value). Then you can compare the last counter value with the last one >> you had and send the response to your users. A WebDNA trigger should >> be fine. >> >> You could also flag the event with just a "1" in your witness >> database, then reset it to "0" each time you send the notification to >> your users. >> >> You can also use the [FileInfo] and [ModTime] but it will not work >> with the WebDNA database, since it is not written to disk. I guess >> this would also be slower. >> >> There are many ways to do this. >> >> chris Jason ? ;-), the default 6.0a install deals with triggers just fine. Just don't edit the default checkboxes when allocating triggers. Yes, there is new code in CICADA that deals with this issue, but I have not had time to test it thoroughly. Regarding triggers. I would suggest to never trust a tcp hit for a time sensitive based call. Instead, trust your computer clock... meaning, use triggers to hit a page many times redundantly in, or around the time sensitive are, with the idea that if the first one misses, the second or third one will hit. Then, control your time sensitive code on the page that is hit.. using [date][time] etc.. Now, it is rare that a tcp hit would fail, but you have more control over your machine than you do the internet... so controlling the time in the code that is hit by the triggers usually works much better. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 770-3822 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Timer (Patrick McCormick 2009)
  2. Re: [WebDNA] Timer ("Jason Adams" 2009)
  3. Re: [WebDNA] Timer ("Psi Prime, Matthew A Perosi " 2009)
  4. Re: [WebDNA] Timer (Terry Wilson 2009)
  5. Re: [WebDNA] Timer (Terry Wilson 2009)
  6. Re: [WebDNA] Timer (Donovan Brooke 2009)
  7. Re: [WebDNA] Timer ("Jason Adams" 2009)
  8. Re: [WebDNA] Timer (christophe.billiottet@webdna.us 2009)
  9. Re: [WebDNA] Timer ("Jason Adams" 2009)
  10. Re: [WebDNA] Timer (Dylan Wood 2008)
  11. [WebDNA] Timer ("Jason Adams" 2008)
Jason Adams wrote: > Hi Chris, > > I do not mean to offend but I find no reports of "trigger bugs fixed" > in the mail list archive. Instead I see several reports of failed > triggers over a long time, including this post made just days ago: > >>> WebDNA Version 6 >>> In the ISP Sandbox settings there are "Sandbox Options" >>> for Emailer and triggers. >> These are buggy in 6.0a so keep them checked on that >> version. They should be fixed in the CICADA (6.1.x build) >> but, I have yet to test the fix thoroughly. > > In this post Mr. Brooke seems to feel the bug may not yet be fixed > even in the new version, thus I hesitate to trust triggers given the > fact that timed event actions are mission critical for us. > > On 1/3/09, christophe.billiottet@webdna.us > wrote: >> A way to do that would be to add a "timestamp" to a small "witness >> database" with only one record, any time the main database or the file >> is updated (you must add a small [replace] command to update the last >> value). Then you can compare the last counter value with the last one >> you had and send the response to your users. A WebDNA trigger should >> be fine. >> >> You could also flag the event with just a "1" in your witness >> database, then reset it to "0" each time you send the notification to >> your users. >> >> You can also use the [fileinfo] and [ModTime] but it will not work >> with the WebDNA database, since it is not written to disk. I guess >> this would also be slower. >> >> There are many ways to do this. >> >> chris Jason ? ;-), the default 6.0a install deals with triggers just fine. Just don't edit the default checkboxes when allocating triggers. Yes, there is new code in CICADA that deals with this issue, but I have not had time to test it thoroughly. Regarding triggers. I would suggest to never trust a tcp hit for a time sensitive based call. Instead, trust your computer clock... meaning, use triggers to hit a page many times redundantly in, or around the time sensitive are, with the idea that if the first one misses, the second or third one will hit. Then, control your time sensitive code on the page that is hit.. using [date][time] etc.. Now, it is rare that a tcp hit would fail, but you have more control over your machine than you do the internet... so controlling the time in the code that is hit by the triggers usually works much better. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 770-3822 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Donovan Brooke

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:

WebCat B13 Mac CGI -- Frames question (1997) Search Command, multiple dbs, etc. --further elucidation needed (2000) [OT] Bad Cookie / Internet Option / Internet Explorer (2004) Waitforfile question (2004) carriage returns in data (1997) Using Plug-In while running 1.6.1 (1997) foreign character sets and conversions (1998) ExclusiveLock (2000) PIXO support (1997) Multiple Pulldowns (1997) WCf2 and nested tags (1997) Only charge card when product shipped ? (1997) HELP WITH DATES (1997) WebCat for Unix?? (1997) ODBC on OS 9 (2003) Why does lineitems loop in sendmail = crash ? (2000) Error:Too many nested [xxx] contexts (1997) RE: 2nd WebCatalog2 Feature Request (1996) [WebDNA] Crashing Database (2011) Re:Emailer and encryption (1997)