Hello, On 29/09/2010 16:03, Jason P Sage wrote: > In this situation - I MIGHT make a "Test" routine that at start up > does a multi-threaded (potentially multi-process) test... that sends a > request and perhaps stores a START DATETIME (memory or a drop > file..whatever) - that upon return updates END DATETIME.
I think that's a good idea. He could show a modal window that enters a loop of checking a variable (updateable using Synchronize from the auxiliar thread), sleep(10) and Application.ProcessMessages (to avoid freezing the GUI), checking also a more sensible timeout as you say. > Meanwhile process or thread #2 - monitors this... (separate process > might help if the OS or Firewall somehow freezes your application .. all > threads or something odd like that) I believe it would make things worse. ZoneAlarm and family work in a process by process basis. If you use another exe, when the user sets the exception, it would give permissions to the auxiliar exe, while the main exe will be still banned. Even the same program when recompiled fires up the firewall again!! That's very annoying when you are programming, so it's better to disable the firewall... or putting most of the program code in a DLL and leaving the exe just as a launching stub. -- saludos, Nico ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
