[storm] storm, mysql and ping

[Sean Allen]

we are moving code over to using storm that was run using perl's  
Apache::DBI.

As Apache::DBI is built in part around using mysql's ping to keep long  
running connections open,
we dont have any transactional code and run with auto commit on by  
default.

eventually we will move away from that but in the meantime, without  
modifying the storm
code is there a way to override the raw_connection.ping(False) call so  
that ping is used?

we could catch disconnect errors but right now we would just be doing  
what ping does
so i don't see much point in not just using ping.

is there a reason with how storm operates that this would cause  
problems?
if yes, any suggestions for the least painful way to handle?
aka least code rewriting on our part...