RequestHandler Processing after Browser is closed...

Hello techies,I have used Browserbegone() in my requesthandler execute method and call my custom script to do processing after browerbegone() eg. $mymodule.Utils.DoProcess()My question is if the browser window is cloesed by end user will the back end process be completed or it will be halted at the point when user closed browser???Thanks,Pravin.

Find more posts tagged with

Comments

sıɹɥɔ

Message from Chris Webster <cwebster@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hi Pravin,

Yes, your process continues on to completion: the user could have closed the browser window, and even shutdown their system; your process will not be interrupted. BrowserBegone() generates the output for the requestHandler (typically a weblingo page), closes the network connection, and then your following code continues execution. When your Execute() script finally does end, the requestHandler's output generation is skipped. So, everything completes; it's just that a) the ordering has changed and b) the requestHandler cannot access the network connection after BrowserBegone() has been called.

Hope this helps,

-chris

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: Thursday, November 20, 2008 4:32 AM
To: eLink Recipient
Subject: RequestHandler Processing after Browser is closed...

RequestHandler Processing after Browser is closed...

Posted by scoruser6 (Alhat, Pravin) on 11/20/2008 05:28 AM

Hello techies,

I have used Browserbegone() in my requesthandler execute method and call my custom script to do processing after browerbegone() eg. $mymodule.Utils.DoProcess()

My question is if the browser window is cloesed by end user will the back end process be completed or it will be halted at the point when user closed browser???

Thanks,
Pravin.

Pravs4

Thanks a lot Chris... You answered it all..Pravin.

Appu_Nair

Also typically OT programmers and people like us are supposed to use the llcache object so even after a re-start you can continue working.Case in Point-Category upgrade of 2 million items.The meta refesh window set to about 20 itemsThe LL RH burns a cacheid into llacache with the nodecrawler params.Somebody in the org does the windows maintenance and re-boots the LLRH running server.The screen now says SDNR.You can refresh the screen and it will start processing from that point on(Obviously there is a cache agent in play here so it has cleared it won't work but I belive the objects stays around three days until completion).I had to use this method for an extraction routine and aws quite impressed by its implementation.Very Good Work OT.And obvioulsy good people like Chris who helps out of the way.