|
> . . . But, changes made to the file from other sources won't fire your listener because > those other sources don't know anything about your listener. The > AS400File object doesn't have any sort of capability to sit on a file > and watch for changes and then fire your listener. I see. Seems rather silly to have a change listener that only listens for changes its own program makes. At any rate, since the ultimate goal is to monitor an event file for business integration, and I'll have full control over the process of adding new events to the file, there's nothing stopping me from putting something into a data queue (which I understand I CAN monitor) whenever I do so. (Using a data queue AS the event file is another possibility, but one that opens up other cans of worms.) -- JHHL
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.