On 3/30/07, Bill Anderson [EMAIL PROTECTED] wrote:
From VFP I can get a message from Windows that a file has been placed
within a directory and in theory pass it off to the handler to process
it. I haven't written the handler portion (I'll get there) but in theory
the handler will try to
I'd suggest you recieve the message and log it to a queue (a DBF),
then return to waiting. Either with a separate process, or with a
timer in the same, scan the queue, determine if there's more work to
be done, do it, and remove the entry from the queue. That way, if
someone drags a dozen
Hi Bill,
Not sure about the BindEvents() solution, but I implemented a timer-based one
as you noted. It was
designed to meet 200 requests in a day (nothing by anyone's standards). It
polled the folder every
minute when the timer triggered. I tested the solution I created with several
hundred
Ted Roche wrote:
On 3/30/07, Bill Anderson [EMAIL PROTECTED] wrote:
From VFP I can get a message from Windows that a file has been placed
within a directory and in theory pass it off to the handler to process
it. I haven't written the handler portion (I'll get there) but in theory
the
Derek Kalweit wrote:
What's wrong with the traditional timer-based file-detection approach?
I've very successfully implemented performance-critical complex apps
with this method and it's never been a problem. If you need a
responsive GUI for it, you can always put DOEVENTS in your loop...
Rick Schummer wrote:
Hi Bill,
Anyway, I don't see any reason to get all fancy with BindEvents() when a
timer works just fine. The
only advantage to BindEvents() is to get instant processing instead of
waiting until the next timer
event.
I think for the first shot out of the gate, I'll
Ted Roche wrote:
Long time, no see, Mr. Anderson.
I'd suggest you recieve the message and log it to a queue (a DBF),
then return to waiting. Either with a separate process, or with a
timer in the same, scan the queue, determine if there's more work to
be done, do it, and remove the entry
7 matches
Mail list logo
