RE: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations
This WebDNA talk-list message is from 2014
It keeps the original formatting.
numero = 111715
interpreted = N
texte = This is a multi-part message in MIME format. ------=_NextPart_000_0526_01D0121B.2E662F10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Steve for the assist. I may be a tad confused but refreshing to = the next URL =E2=80=9C[returnto]=E2=80=9D variable which would be the = original form entry page, simply means that the browser=E2=80=A6.. =20 a) First goes to the =E2=80=9CProcessing Page=E2=80=9D and dump the = form variables there b) Waits to timeout based on the refresh setting c) Then moves the [returnto] page with form variables d) The processing actual then starts =E2=80=A6. =20 However, the page would still timeout on the [returnto] page = wouldn=E2=80=99t it since that is where the processing is done. Sorry if = I am over thinking this but I am definitely confused. The way you employ = the refresh tag here is very much like [redirect] =E2=80=A6.does not = really solve my problem of browser page timing out before getting = response that job is done. =20 Cheers TDn =20 From: Steve Raslevich [mailto:WebDNA@northernsoundandlight.com]=20 Sent: Sunday, December 07, 2014 12:17 To: talk@webdna.us Subject: Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA = Operations =20 Hi Terry, This is a bit of a hack but it works. Here goes.... Create a template with a meta refresh:
Processing Request... Then direct your form to post to the 'Processing Request' page and add a = variable containing the path to the page your form originally posted.=20 Best Regards, Steve Terry Nair wrote:=20 Hi All, =20 Every end of the month, we clean up our entire membership database and = reset earn points, besides other parameters based on computational = norms. This is processed using WebDNA and we have been doing this = without issue for years. Once the lengthy process, initiated via a = browser url link is initiated, it may take anywhere from 8 to 10 minutes = before the "It is done" page is returned ....i.e. end of the process. =20 Well, our database have grown so large that now ....it is taking 15 = minutes to complete the process. WebDNA is not an issue because we can = see it happily doing its thing but ....the browser which is waiting for = the return page ....times out. I need to get the browser response page = back so as to know when to begin the next phase. Right now, when the = browser times out ....I remote into the server and check the Task = Manager which tells me when WebDNA has done its thing. Not elegant but = it works. =20 Breaking up the DB into smaller chunks to be processed separately is = one way to go ....however, was wondering if any of you guys can suggest = a better way of doing this ....getting the response I need when the job = is done. Being informed via SMS or email is not an option. =20 Thank for the assist folks. =20 Cheers Terry Nair =20 =20 --------------------------------------------------------- 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 Bug Reporting: = support@webdna.us=20 --------------------------------------------------------- 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 Bug Reporting: = support@webdna.us ------=_NextPart_000_0526_01D0121B.2E662F10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
= Thanks Steve for the assist. I may be a tad confused but refreshing to = the next URL =E2=80=9C[returnto]=E2=80=9D variable which would be the = original form entry page, simply means that the = browser=E2=80=A6..
=
= a) = First goes to the =E2=80=9CProcessing Page=E2=80=9D and dump the form = variables there
= b) = Waits to timeout based on the refresh setting
= c) = Then moves the [returnto] page with form = variables
= d) = The processing actual then starts =E2=80=A6.
=
= However, the page would still timeout on the [returnto] page = wouldn=E2=80=99t it since that is where the processing is done. Sorry if = I am over thinking this but I am definitely confused. The way you employ = the refresh tag here is very much like [redirect] =E2=80=A6.does not = really solve my problem of browser page timing out before getting = response that job is done.
=
= Cheers TDn
=
From: Steve Raslevich [mailto:WebDNA@northernsoundandlight.com] =
Sent: Sunday, December 07, 2014 12:17
To: = talk@webdna.us
Subject: Re: [WebDNA] Circumnavigate Browser = Timeout On Lengthy WebDNA Operations
Hi = Terry,
This is a bit of a hack but it works. Here = goes....
Create a template with a meta = refresh:
<html>
<head>
<meta = http-equiv=3D"refresh" = content=3D"0;URL=3D[returnto]?[formvariables][name]=3D[url][value][/= url]&[/formvariables]">
</head>
<body>
P= rocessing Request...
</body>
</html>
Then = direct your form to post to the 'Processing Request' page and add a = variable containing the path to the page your form originally posted. =
Best Regards,
Steve
Terry Nair wrote: =
Hi All,
Every = end of the month, we clean up our entire membership database and reset = earn points, besides other parameters based on computational norms. This = is processed using WebDNA and we have been doing this without issue for = years. Once the lengthy process, initiated via a browser url link is = initiated, it may take anywhere from 8 to 10 minutes before the "It = is done" page is returned ....i.e. end of the = process.
Well, our database have grown so large that now = ....it is taking 15 minutes to complete the process. WebDNA is not an = issue because we can see it happily doing its thing but ....the browser = which is waiting for the return page ....times out. I need to get = the browser response page back so as to know when to begin the next = phase. Right now, when the browser times out ....I remote into the = server and check the Task Manager which tells me when WebDNA has done = its thing. Not elegant but it works.
Breaking up the DB into smaller chunks to be = processed separately is one way to go ....however, was wondering = if any of you guys can suggest a better way of doing this ....getting = the response I need when the job is done. Being informed via SMS or = email is not an option.
Thank = for the assist folks.
Cheers = Terry Nair
=
-------------------------------------------------------= -- 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 Bug Reporting: support@webdna.us =
----------------------------------------------= ----------- 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 Bug Reporting: support@webdna.us=
------=_NextPart_000_0526_01D0121B.2E662F10--
Associated Messages, from the most recent to the oldest:
This is a multi-part message in MIME format. ------=_NextPart_000_0526_01D0121B.2E662F10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Steve for the assist. I may be a tad confused but refreshing to = the next URL =E2=80=9C[returnto]=E2=80=9D variable which would be the = original form entry page, simply means that the browser=E2=80=A6.. =20 a) First goes to the =E2=80=9CProcessing Page=E2=80=9D and dump the = form variables there b) Waits to timeout based on the refresh setting c) Then moves the [returnto] page with form variables d) The processing actual then starts =E2=80=A6. =20 However, the page would still timeout on the [returnto] page = wouldn=E2=80=99t it since that is where the processing is done. Sorry if = I am over thinking this but I am definitely confused. The way you employ = the refresh tag here is very much like
[redirect] =E2=80=A6.does not = really solve my problem of browser page timing out before getting = response that job is done. =20 Cheers TDn =20 From: Steve Raslevich [mailto:WebDNA@northernsoundandlight.com]=20 Sent: Sunday, December 07, 2014 12:17 To: talk@webdna.us Subject: Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA = Operations =20 Hi Terry, This is a bit of a hack but it works. Here goes.... Create a template with a meta refresh:
[formvariables][name]=3D
[url][value][/url]&= [/formvariables]"> Processing Request... Then direct your form to post to the 'Processing Request' page and add a = variable containing the path to the page your form originally posted.=20 Best Regards, Steve Terry Nair wrote:=20 Hi All, =20 Every end of the month, we clean up our entire membership database and = reset earn points, besides other parameters based on computational = norms. This is processed using WebDNA and we have been doing this = without issue for years. Once the lengthy process, initiated via a = browser url link is initiated, it may take anywhere from 8 to 10 minutes = before the "It is done" page is returned ....i.e. end of the process. =20 Well, our database have grown so large that now ....it is taking 15 = minutes to complete the process. WebDNA is not an issue because we can = see it happily doing its thing but ....the browser which is waiting for = the return page ....times out. I need to get the browser response page = back so as to know when to begin the next phase. Right now, when the = browser times out ....I remote into the server and check the Task = Manager which tells me when WebDNA has done its thing. Not elegant but = it works. =20 Breaking up the DB into smaller chunks to be processed separately is = one way to go ....however, was wondering if any of you guys can suggest = a better way of doing this ....getting the response I need when the job = is done. Being informed via SMS or email is not an option. =20 Thank for the assist folks. =20 Cheers Terry Nair =20 =20 --------------------------------------------------------- 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 Bug Reporting: = support@webdna.us=20 --------------------------------------------------------- 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 Bug Reporting: = support@webdna.us ------=_NextPart_000_0526_01D0121B.2E662F10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
= Thanks Steve for the assist. I may be a tad confused but refreshing to = the next URL =E2=80=9C[returnto]=E2=80=9D variable which would be the = original form entry page, simply means that the = browser=E2=80=A6..
=
= a) = First goes to the =E2=80=9CProcessing Page=E2=80=9D and dump the form = variables there
= b) = Waits to timeout based on the refresh setting
= c) = Then moves the [returnto] page with form = variables
= d) = The processing actual then starts =E2=80=A6.
=
= However, the page would still timeout on the [returnto] page = wouldn=E2=80=99t it since that is where the processing is done. Sorry if = I am over thinking this but I am definitely confused. The way you employ = the refresh tag here is very much like [redirect] =E2=80=A6.does not = really solve my problem of browser page timing out before getting = response that job is done.
=
= Cheers TDn
=
From: Steve Raslevich [mailto:WebDNA@northernsoundandlight.com] =
Sent: Sunday, December 07, 2014 12:17
To: = talk@webdna.us
Subject: Re: [WebDNA] Circumnavigate Browser = Timeout On Lengthy WebDNA Operations
Hi = Terry,
This is a bit of a hack but it works. Here = goes....
Create a template with a meta = refresh:
<html>
<head>
<meta = http-equiv=3D"refresh" = content=3D"0;URL=3D[returnto]?[formvariables][name]=3D[url][value][/= url]&[/formvariables]">
</head>
<body>
P= rocessing Request...
</body>
</html>
Then = direct your form to post to the 'Processing Request' page and add a = variable containing the path to the page your form originally posted. =
Best Regards,
Steve
Terry Nair wrote: =
Hi All,
Every = end of the month, we clean up our entire membership database and reset = earn points, besides other parameters based on computational norms. This = is processed using WebDNA and we have been doing this without issue for = years. Once the lengthy process, initiated via a browser url link is = initiated, it may take anywhere from 8 to 10 minutes before the "It = is done" page is returned ....i.e. end of the = process.
Well, our database have grown so large that now = ....it is taking 15 minutes to complete the process. WebDNA is not an = issue because we can see it happily doing its thing but ....the browser = which is waiting for the return page ....times out. I need to get = the browser response page back so as to know when to begin the next = phase. Right now, when the browser times out ....I remote into the = server and check the Task Manager which tells me when WebDNA has done = its thing. Not elegant but it works.
Breaking up the DB into smaller chunks to be = processed separately is one way to go ....however, was wondering = if any of you guys can suggest a better way of doing this ....getting = the response I need when the job is done. Being informed via SMS or = email is not an option.
Thank = for the assist folks.
Cheers = Terry Nair
=
-------------------------------------------------------= -- 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 Bug Reporting: support@webdna.us =
----------------------------------------------= ----------- 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 Bug Reporting: support@webdna.us=
------=_NextPart_000_0526_01D0121B.2E662F10--
"Terry Nair"
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:
Lock out multiple users with same password? (1999)
Frames and WebCat (1997)
Dumb Question about Docs (1997)
emailer truncates last letter! (1997)
can webcat determine an image's pixel dimensions? (2000)
Sorting (2005)
[WebDNA] Raspberry Pi (2013)
WebCommerce: Folder organization ? (1997)
[OT] Site launch (2004)
controlling user input (1998)
[math] with first letter in field? (1997)
Protect (1997)
WebCat2.0 [format thousands .0f] no go (1997)
SUBMIT buttons not working.... (2000)
File upload (2002)
WebDNA module - Automated database archiving (1997)
Cant open pages generated by Webcat (2004)
SSL (1998)
Setting up WebCatalog with Retail Pro data (1996)
RE: New WebCatalog Version !!! (1997)