Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) Standard preamble: ========================================================================
NAMEDBD::Gofer::Transport::stream - DBD::Gofer transport for stdio streaming
or, enable by setting the
DESCRIPTIONWithout the "url=" parameter it launches a subprocess as
perl -MDBI::Gofer::Transport::stream -e run_stdio_hex
and feeds requests into it and reads responses from it. But that's not very useful.
With a "url=ssh:email@example.com" parameter it uses ssh to launch the subprocess on a remote system. That's much more useful!
It gives you secure remote access to
The actual command invoked is something like:
ssh -xq ssh:firstname.lastname@example.org bash -c $setup $run
where $run is the command shown above, and $command is
. .bash_profile 2>/dev/null || . .bash_login 2>/dev/null || . .profile 2>/dev/null; exec "$@"
which is trying (in a limited and fairly unportable way) to setup the environment (
The ""perl"" used in the command will default to the value of $^X when not using ssh. On most systems that's the full path to the perl that's currently executing.
PERSISTENCECurrently gofer stream connections persist (remain connected) after all database handles have been disconnected. This makes later connections in the same process very fast.
Currently up to 5 different gofer stream connections (based on url) can persist. If more than 5 are in the cache when a new connection is made then the cache is cleared before adding the new connection. Simple but effective.
TO DODocument go_perl attribute
Automatically reconnect (within reason) if there's a transport error.
Decide on default for persistent connection - on or off? limits? ttl?
AUTHORTim Bunce, <www.tim.bunce.name>
LICENCE AND COPYRIGHTCopyright (c) 2007, Tim Bunce, Ireland. All rights reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See perlartistic.