Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111718
interpreted = N
texte = This is a multi-part message in MIME format. --------------070600070300040105080205 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Terry Nair wrote: > > Thanks Steve for the assist. I may be a tad confused but refreshing to=20 > the next URL =E2=80=9C[returnto]=E2=80=9D variable which would be the o= riginal form=20 > 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 for= m 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. > The processing begins when the 'processing page' is hit and loaded and=20 the variables are immediately forwarded to the url specified in my=20 [returnto] variable. So now the browser is showing the processing page=20 and [returnto] page will not load until the job is completed. > > However, the page would still timeout on the [returnto] page wouldn=E2=80= =99t=20 > it since that is where the processing is done. Sorry if I am over=20 > thinking this but I am definitely confused. The way you employ the=20 > refresh tag here is very much like [redirect] =E2=80=A6.does not really= solve=20 > my problem of browser page timing out before getting response that job=20 > 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=20 > WebDNA Operations > > Hi Terry, > > This is a bit of a hack but it works. Here goes.... > > Create a template with a meta refresh: > > > > content=3D"0;URL=3D[returnto]?[formvariables][name]=3D[url][value][/url= ]&[/formvariables]"> > > > Processing Request... > > > > > Then direct your form to post to the 'Processing Request' page and add=20 > 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=20 > reset earn points, besides other parameters based on computational=20 > norms. This is processed using WebDNA and we have been doing this=20 > without issue for years. Once the lengthy process, initiated via a=20 > browser url link is initiated, it may take anywhere from 8 to 10=20 > minutes before the "It is done" page is returned ....i.e. end of the=20 > process. > > Well, our database have grown so large that now ....it is taking 15=20 > minutes to complete the process. WebDNA is not an issue because we can=20 > see it happily doing its thing but ....the browser which is waiting=20 > for the return page ....times out. I need to get the browser response=20 > page back so as to know when to begin the next phase. Right now, when=20 > the browser times out ....I remote into the server and check the Task=20 > Manager which tells me when WebDNA has done its thing. Not elegant but=20 > it works. > > Breaking up the DB into smaller chunks to be processed separately is=20 > one way to go ....however, was wondering if any of you guys can=20 > suggest a better way of doing this ....getting the response I need=20 > 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=20 > is sent to you because you are subscribed to the mailing list . To=20 > unsubscribe, E-mail to: archives:=20 > http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 > support@webdna.us > > --------------------------------------------------------- This message=20 > is sent to you because you are subscribed to the mailing list . To=20 > unsubscribe, E-mail to: archives:=20 > http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 > support@webdna.us > > --------------------------------------------------------- This message=20 > is sent to you because you are subscribed to the mailing list . To=20 > unsubscribe, E-mail to: archives:=20 > http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 > support@webdna.us=20 --------------070600070300040105080205 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Terry Nair wrote:

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 origina= l form entry page, simply means that the browser=E2=80=A6..

=C2=A0

a)=C2=A0=C2=A0=C2=A0=C2=A0 First goes to the =E2=80=9CProcessing Page=E2=80=9D and dump the form variables= there

b)=C2=A0=C2=A0=C2=A0=C2=A0 Waits to timeout based on the refresh setting

c)=C2=A0=C2=A0=C2=A0=C2=A0 Then moves the [returnto] page with form variables

d)=C2=A0=C2=A0=C2=A0=C2=A0 The processing actual then starts =E2=80=A6.

The processing begins when the 'processing page' is hit and loaded and the variables are immediately forwarded to the url specified in my [returnto] variable. So now the browser is showing the processing page and [returnto] page will not load until the job is completed.

=C2=A0

However, the page would still timeout on the [returnto] page wouldn=E2=80=99t it s= ince 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 o= f browser page timing out before getting response that job is done.

=C2=A0

Cheers TDn

=C2=A0

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

=C2=A0

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]&= amp;[/formvariables]">
</head>
<body>
Processing 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,

=C2=A0

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.

=C2=A0

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.=C2=A0 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.

=C2=A0

Breaking up the DB into smaller chunks to be processed separately=C2=A0 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.

=C2=A0

Thank for the assist folks.

=C2=A0

Cheers Terry Nair

=C2=A0

=C2=A0

------------------------------------------------= --------- 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

--------------------------------------------------------- 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 --------------070600070300040105080205-- Associated Messages, from the most recent to the oldest:

    
  1. RE: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations ("Terry Nair" 2014)
  2. Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations (Steve Raslevich 2014)
  3. Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations ("Psi Prime Inc, Matthew A Perosi " 2014)
  4. RE: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations ("Terry Nair" 2014)
  5. Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations (Steve Raslevich 2014)
  6. [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations ("Terry Nair" 2014)
This is a multi-part message in MIME format. --------------070600070300040105080205 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Terry Nair wrote: > > Thanks Steve for the assist. I may be a tad confused but refreshing to=20 > the next URL =E2=80=9C[returnto]=E2=80=9D variable which would be the o= riginal form=20 > 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 for= m 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. > The processing begins when the 'processing page' is hit and loaded and=20 the variables are immediately forwarded to the url specified in my=20 [returnto] variable. So now the browser is showing the processing page=20 and [returnto] page will not load until the job is completed. > > However, the page would still timeout on the [returnto] page wouldn=E2=80= =99t=20 > it since that is where the processing is done. Sorry if I am over=20 > thinking this but I am definitely confused. The way you employ the=20 > refresh tag here is very much like [redirect] =E2=80=A6.does not really= solve=20 > my problem of browser page timing out before getting response that job=20 > 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=20 > WebDNA Operations > > Hi Terry, > > This is a bit of a hack but it works. Here goes.... > > Create a template with a meta refresh: > > > > content=3D"0;URL=3D[returnto]?[formvariables][name]=3D[url][value][/url= ]&[/formvariables]"> > > > Processing Request... > > > > > Then direct your form to post to the 'Processing Request' page and add=20 > 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=20 > reset earn points, besides other parameters based on computational=20 > norms. This is processed using WebDNA and we have been doing this=20 > without issue for years. Once the lengthy process, initiated via a=20 > browser url link is initiated, it may take anywhere from 8 to 10=20 > minutes before the "It is done" page is returned ....i.e. end of the=20 > process. > > Well, our database have grown so large that now ....it is taking 15=20 > minutes to complete the process. WebDNA is not an issue because we can=20 > see it happily doing its thing but ....the browser which is waiting=20 > for the return page ....times out. I need to get the browser response=20 > page back so as to know when to begin the next phase. Right now, when=20 > the browser times out ....I remote into the server and check the Task=20 > Manager which tells me when WebDNA has done its thing. Not elegant but=20 > it works. > > Breaking up the DB into smaller chunks to be processed separately is=20 > one way to go ....however, was wondering if any of you guys can=20 > suggest a better way of doing this ....getting the response I need=20 > 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=20 > is sent to you because you are subscribed to the mailing list . To=20 > unsubscribe, E-mail to: archives:=20 > http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 > support@webdna.us > > --------------------------------------------------------- This message=20 > is sent to you because you are subscribed to the mailing list . To=20 > unsubscribe, E-mail to: archives:=20 > http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 > support@webdna.us > > --------------------------------------------------------- This message=20 > is sent to you because you are subscribed to the mailing list . To=20 > unsubscribe, E-mail to: archives:=20 > http://mail.webdna.us/list/talk@webdna.us Bug Reporting:=20 > support@webdna.us=20 --------------070600070300040105080205 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Terry Nair wrote:

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 origina= l form entry page, simply means that the browser=E2=80=A6..

=C2=A0

a)=C2=A0=C2=A0=C2=A0=C2=A0 First goes to the =E2=80=9CProcessing Page=E2=80=9D and dump the form variables= there

b)=C2=A0=C2=A0=C2=A0=C2=A0 Waits to timeout based on the refresh setting

c)=C2=A0=C2=A0=C2=A0=C2=A0 Then moves the [returnto] page with form variables

d)=C2=A0=C2=A0=C2=A0=C2=A0 The processing actual then starts =E2=80=A6.

The processing begins when the 'processing page' is hit and loaded and the variables are immediately forwarded to the url specified in my [returnto] variable. So now the browser is showing the processing page and [returnto] page will not load until the job is completed.

=C2=A0

However, the page would still timeout on the [returnto] page wouldn=E2=80=99t it s= ince 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 o= f browser page timing out before getting response that job is done.

=C2=A0

Cheers TDn

=C2=A0

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

=C2=A0

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]&= amp;[/formvariables]">
</head>
<body>
Processing 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,

=C2=A0

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.

=C2=A0

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.=C2=A0 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.

=C2=A0

Breaking up the DB into smaller chunks to be processed separately=C2=A0 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.

=C2=A0

Thank for the assist folks.

=C2=A0

Cheers Terry Nair

=C2=A0

=C2=A0

------------------------------------------------= --------- 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

--------------------------------------------------------- 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
--------------070600070300040105080205-- Steve Raslevich

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:

RE: [sendmail]- bcc? (1998) Million product store (2003) Download (1999) WebCat.acgi from /cgi-bin/? (1997) Bug Report, maybe (1997) Sendmail Excel attachment (2003) Exists? (1997) [ShowNext] feature in 2.0 (1997) Blocking off access (2005) Amusement (2004) Replace context problem ... (1997) RE: protect tag on NT (1997) PROBLEM (1997) You *can!!* overwrite username/password using an HTML form. Also, experts *please* see Q at end (2000) 2.0 Info (1997) AAgghh!! Help, please. SSL strikes again. (1997) Order not created error (1997) Search in 2 or more catalogs (1997) Frames and WebCat (1997) form data submission gets truncated (1997)