Hi Thomas,

I will do. We expect to have this running in the very near future. We have this implemented in 3 independent systems, an Internal E-Mail system, where we use it to notify of new e-mail arrivals, a WorkToDo system (not finished yet, current version uses a timer) where is it used to alert users of some new task that requires they attention and finally for a Maintenance mode warning, where we alert the user that they should shut down their applications or we do it for them <g> and one thing I can tell you now is that the systems seem all to respond to the events almost instantly even when running in 3 or 4 computers, but there is a catch, we do not subscribe to a file, for this event is not reliable, for when the OS detects that a folder is been highly updated, it just skips the file event and just notifies about the folder being updated. To overcome this, what we do is each user subscribes to their own folder to avoid unnecessary updating (and each of this applications have their own tree) rather than all users listening for events on the same folder, and then we adir in search for the special files.


>we may have to implement something similar in the future, and I'd be grateful if you could send me an update on the reliability of this approach. In theory it should get you best response time, but I worry (partially from timer event expirience<bg>) that the event may hiccup or not fire always - as long as enough intervals (or different timers) are in play I see timer usage as the approach "with safety net" - but less elegant.
>
>regards
>
>thomas