Information générale
Catégorie:
Fonctions Windows API
Versions des environnements
>Hola Carlos,
>
>I read that note too when I was writing my code, but then I also saw that it still works in Vista (I did run tests on vista and worked just fine) so I went ahead. We transformed a WorkToDo application that was using a timer and we had lots of complains about it being slow (we needed a relatively fast timer, I think it checked every minute and we even slowed it down to a couple of minutes) but running the same select statement on hundreds of computers "simultaneously" on the network was a speed killer. Now the same application, with the same select statement(s) in the same number of computers (or even more) runs very smoothly, and much much faster and without generating unnecessary network traffic.
Hola Hugo,
I guess it depends in what you have to do. I researched the SHChangeNotifyRegister path when doing an app that interfaces with an old FPDOS 2.6 app that needed to do some web transactions.
I ended up using a timer and adir, I just needed to check for new files in a shared folder in the server, read the file, created by the FPDOS app in the terminals, do a web request with the data in it, delete the file, and create a response file with the same name but a different extension that the FPDOS app would read back.
It has been working great for about 1,5 years now.
Carlos
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement