in reply to binding to a vhost using LWP

As i doubt you could get access to the socket, especially during construction, i'd make a use base relationship with the desired modules, and modify the constructor to create your own type of socket.
I must admit i only skimmed the docs before writing this, and haven't made completely sure, but i'm in doubt that i'm wrong. It's something too specific for a general module. If you do that you can avoid most of the work, because the interface remains essentially the same.

Update: To explicitly decide what interface to bind the outgoing socket to that must be done before connect. My mistake was that i assumed connect happens at construction. You simply need to redefine the method that starts the connection...

-nuffin
zz zZ Z Z #!perl