Re: [WebDNA] Some code inside a large loops fail ... but why?
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104430
interpreted = N
texte = Browsers have timeouts after which they post an error so I don't see why tcpconnect shouldn't have a timeout as well. The default behavior could be no timeout so existing sites don't break or have to be re-coded, but with an optional timeout parameter at least the rest of the code on the page can be processed. In my case of 300,000 loop iterations a tcpconnect failure in the beginning can result in ten or hundreds of thousands of db records not entered -- all because of one simple tcpconnect that failed. I would much rather just skip that one, and any others that fail along the way, then go back later and check the db to see which ones are missing and re-try only those. Sincerely, Kenneth Grome www.KenGrome.com > Ken you are right. > > Now that I think about it, TCP connections that "Time Out" cause problems on my Windows server and basically lock the connection until the WebDNA service is restarted. > > Yes, a time out would be great or any other way of killing the connection. > > Regards > > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au > > > > > On 13/01/2010, at 2:08 PM, Kenneth Grome wrote: > > > Won't work, if the tcpconnect gets stuck the waitforfile won't execute. > > > > Waitforfile only delays the following code, it won't force it to execute. > > > > Sincerely, > > Kenneth Grome > > www.KenGrome.com > > > > > > > > > > > > > > > >> What about a WaitForFile ? > >> > >> Regards > >> > >> Stuart Tremain > >> IDFK Web Developments > >> AUSTRALIA > >> webdna@idfk.com.au > >> > >> > >> > >> > >> On 13/01/2010, at 12:09 PM, Kenneth Grome wrote: > >> > >>> Another question which may lead to new insights here: > >>> > >>> When the tcpconnect fails to get a response, what happens? Does it prevent the rest of the loop from executing? If so, is there some kind of timeout built into tcpconnect that we can use to force the loop to continue after such a tcpconnect freeze/failure? > >> > >> --------------------------------------------------------- > >> This message is sent to you because you are subscribed to > >> the mailing list
. > >> To unsubscribe, E-mail to: > >> archives: http://mail.webdna.us/list/talk@webdna.us > >> old archives: http://dev.webdna.us/TalkListArchive/ > >> Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 > >> > > > > --------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > old archives: http://dev.webdna.us/TalkListArchive/ > > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 >
Associated Messages, from the most recent to the oldest:
Browsers have timeouts after which they post an error so I don't see why tcpconnect shouldn't have a timeout as well. The default behavior could be no timeout so existing sites don't break or have to be re-coded, but with an optional timeout parameter at least the rest of the code on the page can be processed. In my case of 300,000 loop iterations a tcpconnect failure in the beginning can result in ten or hundreds of thousands of db records not entered -- all because of one simple tcpconnect that failed. I would much rather just skip that one, and any others that fail along the way, then go back later and check the db to see which ones are missing and re-try only those. Sincerely, Kenneth Grome www.KenGrome.com > Ken you are right. > > Now that I think about it, TCP connections that "Time Out" cause problems on my Windows server and basically lock the connection until the WebDNA service is restarted. > > Yes, a time out would be great or any other way of killing the connection. > > Regards > > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au > > > > > On 13/01/2010, at 2:08 PM, Kenneth Grome wrote: > > > Won't work, if the tcpconnect gets stuck the waitforfile won't execute. > > > > Waitforfile only delays the following code, it won't force it to execute. > > > > Sincerely, > > Kenneth Grome > > www.KenGrome.com > > > > > > > > > > > > > > > >> What about a WaitForFile ? > >> > >> Regards > >> > >> Stuart Tremain > >> IDFK Web Developments > >> AUSTRALIA > >> webdna@idfk.com.au > >> > >> > >> > >> > >> On 13/01/2010, at 12:09 PM, Kenneth Grome wrote: > >> > >>> Another question which may lead to new insights here: > >>> > >>> When the tcpconnect fails to get a response, what happens? Does it prevent the rest of the loop from executing? If so, is there some kind of timeout built into tcpconnect that we can use to force the loop to continue after such a tcpconnect freeze/failure? > >> > >> --------------------------------------------------------- > >> This message is sent to you because you are subscribed to > >> the mailing list . > >> To unsubscribe, E-mail to: > >> archives: http://mail.webdna.us/list/talk@webdna.us > >> old archives: http://dev.webdna.us/TalkListArchive/ > >> Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 > >> > > > > --------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > old archives: http://dev.webdna.us/TalkListArchive/ > > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 >
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:
numfound question (2005)
Non-Cart Files in Shopping Cart Folder (1997)
Apache 2.x .tpl mime types config? (2005)
Forms Search Questions (1997)
Search design (1997)
[SQL] on MacOs to SQL Server ... HOW TO? (2000)
Overridding E-Mailer (1998)
WebCat2 several catalogs? (1997)
Exclamation point (1997)
and more [shipcost].... (2001)
Altivec (Velocity engine) (2000)
problem: search crashes webstar (1997)
WebCatalog2 Feature Feedback (1996)
Help with Repost Data msg from form (1997)
Can't load tmpl files (1997)
Emailer (1998)
Almost a there but..bye bye NetCloak (1997)
WebCatalog dying in NT (1998)
read and write you own cookies with webcat (1997)
GrandTotal not right (1997)