![]() |
Pedro Rocadas <procadas@yahoo.com> writes: >> WHFC (and Cypheus) *polls* server each predefined >> time interval, say 60 >> sec. It means that the status of your job cannot be >> updated more >> frequently. It also means, that if you have 60 >> clients in your network, and >> all of them are idle, the Hylafax server still will >> be busy processing >> their queries. On the contrary, Hylafax triggers >> implement event driven >> model, when Hylafax immediately informs the client >> that some interesting >> event has happened. AFAIK, none of existing Windows >> cliens can utilize >> this feature. > > You want update times less than 60 secs?? Generally, a > fax spent 1 min or more to be delivered (depending in > how "complex" is your job). I know because our jobs > are very light. I have periods of considerable > workloads and I never saw hylafax degradation. Your > users are so "paranoid" that they want a notification > if the first attempt failled? Mine just want Ok:good > Failled:resend. They like to see the job in progress :-) See the attached screenshot to see how it's going on.
- Dmitry Bely