I'm using WWW::Mechanize and checking for success(). Which should mean a non-error HTTP status code, if memory serves correctly. I have to dig deeper into this, there are most likely error conditions i don't check for. I have to simulate a few types of network errors to see how WWW::Mechanize handles these. (*)
My stuff is still a bit alpha. Basically, i use a couple of half-hour lunch breaks this week to plonk in some extra logging into my existing chatterbot codebase, write a function to run a SELECT statement for the statistics and use existing code to update a Node on PM.
Today i was also playing around with the code and updating the database and stuff. Plus doing a linux update, which took the whole thing offline for a few minutes. I'm not exactly sure how long chatterbot was offline today or exactly when (Lunchbreaks don't always happen at noon for me, it's more like a "when i'm hungry and i can spare the time" thing).
(*) Most of my day-to-day dev work is web server development. Strangely enough, i hardly ever implement client code.
In reply to Re^9: super slow
by cavac
in thread super slow
by Danny
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |