|
Point well made. (Slap myself on the forehead) >>> <rob@dekko.com> 03/13/02 11:10AM >>> The problem with the exit point is that it is a before. It was designed as a security measure. For example if you process the event it will be like the following Client: May I send you this file? Server: Yes. Let me post the data. Done. Ok, now start sending. Client: Sending data Done. See you're posting the data prior to receipt. There are a few tricks around this. 1) Submit a job from the exit point. Put a delay in this job sufficient enough to wait until the data is received. Or do other things like a small delay and then an existence and lock check. 2) Have the user send you two files. Trigger your process off of the second file. Our partners do the remote command. Except for one. He was running AIX and claimed that he could not get the QUOTE RCMD to work. We used the dummy second file with them. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "alan shore" <SHOREA@dime.com> To: <midrange-l@midrange.com> Sent by: cc: midrange-l-admin@mi Fax to: drange.com Subject: Re: system event trigger whenever a source file member is updated 03/13/2002 10:47 AM Please respond to midrange-l How about using the FTP exit point. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.