[WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111713
interpreted = N
texte = This is a multi-part message in MIME format. ------=_NextPart_000_0516_01D01203.42AA18F0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 ------=_NextPart_000_0516_01D01203.42AA18F0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

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

 

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.

 

Thank = for the assist folks.

 

Cheers = Terry Nair

 

=  

------=_NextPart_000_0516_01D01203.42AA18F0-- 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. ------=_NextPart_000_0516_01D01203.42AA18F0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 ------=_NextPart_000_0516_01D01203.42AA18F0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

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

 

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.

 

Thank = for the assist folks.

 

Cheers = Terry Nair

 

=  

------=_NextPart_000_0516_01D01203.42AA18F0-- "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:

WebCat2b12 forgets serial # (1997) Problem with version 4 browsers (1998) New index for docs (1997) RE: combining strings (1997) webcat2b12 CGI -- Date comparisons (1997) Sending an email to all )or some) email addresses int he database (1999) Mac: [ListFiles] bug alert (1997) [isfile] ? (1997) [TaxableTotal] - not working with AOL and IE (1997) Cookie question (1999) Sitebuilder (2004) [WebDNA] PayPal Express Checkout (2009) RE: [WebDNA] Check for Ending Carriage Return (2009) Interface to Quickbooks (2005) quantity minimum problem (1997) Creating main- and sub-category search (1997) [SHOWIF] (1997) Summary search -- speed (1997) problems with 2 tags shakur (1997) WebCat2 several catalogs? (1997)