Threads suck!

Well, not really of course. But the thing is, my ePing.py release with threaded support is probably not really threaded.... It didn't work, so I just put up a revised version which does work, but I fear I broke the Threaded part. Well, first I have to work, but I will try to look into. Maybe I should first read about the basics...

Net result from ePing.py

The company that creates and maintains our web applications apparently seemed to be able to "optimize"their code.

Last week my director asked me to mail an excerpt from the log to them, showing how many timeouts out sites have. They of course give no feedback to me, but the amount of e-mail notifications has been down drastically. And since yesterday, when I put the last version to work with a higher default-timeout of 10 seconds (instead of 5 seconds), I haven't received any notifications at all. Actually, as of now, nothing has been written to the log. So I guess their code optimizations, and the higher timeout value, made this possible.

I started the basic idea actually already in March this year, but started on a completely new code around July, and under a different name. And it seems that it has already paid of for my employer... Since it's a e-tailer, any downtime is possible missed orders...

Progress on ePing.py going slowly but surely

I just put the source of v0.04 online on Google Code. Main new thing in this version is that the UrlChecker class now runs threaded. This means that one run of ePing.py will not last longer if more URL's are to be checked (previously one check lasted more then 8 minutes when several of my employers website where unreachable).