Appropriate to the goal, but the module is just going to give you the tools you need to write query-killing features, rather than actually doing it for you. Every application is going to have unique circumstances about how to connect to the database, so I'm not sure how I could build that into the module.
So, as it stands, it is just the piece that watches for the socket to get disconnected, and "does stuff" that you tell it to do, like send signals, close connections to hosts, or exec external commands. | [reply] |
Hello NERDVANA,
> ..watches for the socket to get disconnected, and "does stuff"
so why not something IO::Socket::ManageDisconnected or IO::Socket::GetDisconnected ?
Or if you wont something with more humor.. in Czechia they have a small troll in houses that eats sockets unpairing them.. ask choroba for the name
L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
| [reply]
[d/l]
[select] |
The trolls eat socks, not sockets. They are named "lichožrouti", wich translates to something like odd-eaters. The Oddsocketeaters even have their Wikipedia page and it seems the film exists with English dubbing.
map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
| [reply]
[d/l] |
