From: MenTaLguY <mental@...>
Date: 2008-03-06T04:18:17+09:00
Subject: Re: multithreading sysread error

There are a number of problems, among them:

 1. deriving from Monitor does not do anything for you in
    this case, since you don't use any of its locking
    facilities (deriving from Monitor like this probably
    isn't a good approach anyway)

 2. WWW::Mechanize instances are not safe to share
    between threads; it's best to create a separate agent
    per thread.

 3. Using the Timeout class on complicated libraries
    can often break them.  If you really need operations
    to time out, it is best to see if the library provides
    direct support for timeouts on its operations.

-mental