| Date: | Tue, 24 Aug 2004 22:11:18 -0400 |
| From: | Tom Metro <tmetro [...] cpan.org> |
| To: | bug-libwww-perl [...] rt.cpan.org |
| Subject: | HTTP::Daemon::ClientConn should be decoupled from HTTP::Daemon |
I guess this is best classified as a "Wishlist item."
HTTP::Daemon::ClientConn should be decoupled from HTTP::Daemon, which
would allow users to use HTTP::Daemon::ClientConn (which contains the
bulk of the code) with other daemon modules (such as Net::Daemon,
Net::Server, etc.).
As it is now, you can pull this off by subclassing HTTP::Daemon and
re-implementing a bunch of its methods, but that seems unnecessarily
messy. (I took this approach when using HTTP::Daemon to build a proxy
server along with Net::Server.)
It appears that HTTP::Daemon::ClientConn could be tweaked to reduce or
eliminate the coupling.
I'd be happy to donate the code to do this, if there is interest. (I
don't want to do this on speculation, as I don't think it is significant
enough to warrant forking the module, and in my experience, module
maintainers are usually reluctant to accept patches of this nature if
they don't fit their vision of how the module should be architected.)
-Tom