Ok, so I am working on some very long reports and am peddling ideas...
Here's the idea: The user runs a very long report, and the request will
simply be placed in some sort of queue to be ran asynchronously. The
user is told he/she will be notified when it is completed.
Then the user surfs
Subject: No, I'll call you...
Ok, so I am working on some very long reports and am peddling ideas...
Here's the idea: The user runs a very long report, and the request will
simply be placed in some sort of queue to be ran asynchronously. The
user is told he/she will be notified when it is completed
This probably isn't what you want either, but...
You could have your report program write to a table when it's complete.
The record would consist of who needs to be notified, and the status of
their notification. Maybe the session ID or some session variable could
be stored.
Then you could
We have a similar architecture at my work where those long reports are sent
as an Async request (Async Gateway) and then user is notified via email when
reports are complete.
Thanks
On 12/21/06, Christopher Jordan [EMAIL PROTECTED] wrote:
This probably isn't what you want either, but...
You
at http://www.reedexpo.com
-Original Message-
From: Christopher Jordan
To: CF-Talk
Sent: Thu Dec 21 17:04:02 2006
Subject: Re: No, I'll call you...
This probably isn't what you want either, but...
You could have your report program write to a table when it's complete.
The record would
]
Sent: Thursday, December 21, 2006 11:04 AM
To: CF-Talk
Subject: Re: No, I'll call you...
This probably isn't what you want either, but...
You could have your report program write to a table when it's complete.
The record would consist of who needs to be notified, and the status
Yes, I believe so. But isn't that limited to CF Enterprise? We only
have standard. *sigh*
~Brad
-Original Message-
From: Robertson-Ravo, Neil (RX)
[mailto:[EMAIL PROTECTED]
Sent: Thursday, December 21, 2006 11:04 AM
To: CF-Talk
Subject: Re: No, I'll call you...
Isn't this what
:02 2006
Subject: Re: No, I'll call you...
This probably isn't what you want either, but...
You could have your report program write to a table when it's complete.
The record would consist of who needs to be notified, and the status of
their notification. Maybe the session ID or some session
21 17:14:18 2006
Subject: RE: No, I'll call you...
Yes, I believe so. But isn't that limited to CF Enterprise? We only
have standard. *sigh*
~Brad
-Original Message-
From: Robertson-Ravo, Neil (RX)
[mailto:[EMAIL PROTECTED]
Sent: Thursday, December 21, 2006 11:04 AM
To: CF-Talk
-Original Message-
From: Robertson-Ravo, Neil (RX)
[mailto:[EMAIL PROTECTED]
Sent: Thursday, December 21, 2006 11:04 AM
To: CF-Talk
Subject: Re: No, I'll call you...
Isn't this what the Event Gateway in ColdFusion could be used for?
Either
the CFML or a combo of the CFML
If your network will support it, I've done some messaging of this type with NET
SEND called with cfexecute... tags.
HTH
--
Ian Skinner
Web Programmer
BloodSource
www.BloodSource.org
Sacramento, CA
-
| 1 | |
- Binary Soduko
| | |
-
C code. C code
Hmm, I hadn't thought of that. Net set works on my network, but can I
do that from a Linux webserver?
~Brad
-Original Message-
From: Ian Skinner [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 21, 2006 11:55 AM
To: CF-Talk
Subject: RE: No, I'll call you...
If your network
Brad,
We've got an application where the user requests the report, and the actual
report generation is handled by an asynchronous event gateway. When the
gateway is done generating the report, it then generates an email to the
user notifying them that their report is ready. Our users will have
Hmm, I hadn't thought of that. Net set works on my network, but can I do that
from a Linux webserver?
~Brad
I don't know. I don't get to play with Linux very often, but if it doesn't the
web server maybe able to call the NET SEND from another machine if the
appropriate paths and permissions
14 matches
Mail list logo
