-- it seems unnecessary to do a round trip to the client to do this. I
would consider using cfhttp/curl/wget to call the desired template
instead.
--
Hugo Ahlenius
-------------------------------------------------------------
Hugo Ahlenius E-Mail: [EMAIL PROTECTED]
Project Officer Phone: +46 8 230460
UNEP GRID-Arendal Fax: +46 8 230441
Stockholm Office Mobile: +46 733 467111
WWW: http://www.grida.no
-------------------------------------------------------------
| -----Original Message-----
| From: Jim Davis [mailto:[EMAIL PROTECTED]
| Sent: Wednesday, July 14, 2004 17:36
| To: CF-Talk
| Subject: RE: Releasing client to do another process?
|
| Actually your first option would, indeed, complete the
| process - it just couldn't return information to the browser
| when done.
|
|
|
| A CF Process keeps going until it ends or times out - only
| then does it return back to the web server which in turn
| tries to return to the browser.
| If the browser isn't waiting any longer then you get an error
| in your logs, but the process did complete.
|
|
|
| Jim Davis
|
|
|
| From: Micha Schopman [mailto:[EMAIL PROTECTED]
| Sent: Wednesday, July 14, 2004 3:27 AM
| To: CF-Talk
| Subject: RE: Releasing client to do another process?
|
|
|
| This is actually very simple,
|
| 1: Create a page, and within create an iframe 100% high and
| wide. Call,
| parent.doSomething() from the iframe to call the _javascript_
| function in the page where the iframe is.
| This does not complete the process if the user closes the
| window! Only if it browses to another place.
| 2: Create a scheduled task, and run this task immediately.
| When the task is finished remove it. This task is not
| dependant on the browser window clientside. If you need
| session vars etc. in your task, pass them to the task as
| parameters, or find a way to overcome this.
|
|
|
|
|
|
|
|
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
