DBD::Gofer - A stateless-proxy driver for communicating with a remote DBI River stage four • 984 direct dependents • 2505 total dependents

DBD::Gofer is a DBI database driver that forwards requests to another DBI driver, usually in a separate process, often on a separate machine. It tries to be as transparent as possible so it appears that you are using the remote driver directly. DBD::...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Policy::rush - The 'rush' policy for DBD::Gofer River stage four • 984 direct dependents • 2505 total dependents

The "rush" policy tries to make as few round-trips as possible. It's the opposite end of the policy spectrum to the "pedantic" policy. Temporary docs: See the source code for list of policies and their defaults. In a future version the policies and t...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Policy::Base - Base class for DBD::Gofer policies River stage four • 984 direct dependents • 2505 total dependents

DBD::Gofer can be configured via a 'policy' mechanism that allows you to fine-tune the number of round-trips to the Gofer server. The policies are grouped into classes (which may be subclassed) and referenced by the name of the class. The DBD::Gofer:...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Policy::classic - The 'classic' policy for DBD::Gofer River stage four • 984 direct dependents • 2505 total dependents

Temporary docs: See the source code for list of policies and their defaults. In a future version the policies and their defaults will be defined in the pod and parsed out at load-time....

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Transport::http - DBD::Gofer client transport using http River stage zero No dependents

Connect with DBI::Gofer servers that use http transports, i.e., DBI::Gofer::Transport::mod_perl. This module currently uses the LWP::UserAgent and HTTP::Request modules to manage the http protocol. The default timeout is undef (unlimited). The LWP::U...

TIMB/GoferTransport-http-1.017 - 12 Sep 2008 12:25:33 GMT

DBD::Gofer::Transport::null - DBD::Gofer client transport for testing River stage four • 984 direct dependents • 2505 total dependents

Connect via DBD::Gofer but execute the requests within the same process. This is a quick and simple way to test applications for compatibility with the (few) restrictions that DBD::Gofer imposes. It also provides a simple, portable way for the DBI te...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Transport::Base - base class for DBD::Gofer client transports River stage four • 984 direct dependents • 2505 total dependents

This is the base class for all DBD::Gofer client transports....

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Policy::pedantic - The 'pedantic' policy for DBD::Gofer River stage four • 984 direct dependents • 2505 total dependents

The "pedantic" policy tries to be as transparent as possible. To do this it makes round-trips to the server for almost every DBI method call. This is the best policy to use when first testing existing code with Gofer. Once it's working well you shoul...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Transport::stream - DBD::Gofer transport for stdio streaming River stage four • 984 direct dependents • 2505 total dependents

Without 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:username@host.example.com" parameter it...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Transport::pipeone - DBD::Gofer client transport for testing River stage four • 984 direct dependents • 2505 total dependents

Connect via DBD::Gofer and execute each request by starting executing a subprocess. This is, as you might imagine, spectacularly inefficient! It's only intended for testing. Specifically it demonstrates that the server side is completely stateless. I...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Gofer::Transport::corostream - Async DBD::Gofer stream transport using Coro and AnyEvent River stage four • 984 direct dependents • 2505 total dependents

The *BIG WIN* from using Coro is that it enables the use of existing DBI frameworks like DBIx::Class....

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBD::Proxy - A proxy driver for the DBI River stage four • 984 direct dependents • 2505 total dependents

DBD::Proxy is a Perl module for connecting to a database via a remote DBI driver. See DBD::Gofer for an alternative with different trade-offs. This is of course not needed for DBI drivers which already support connecting to a remote database, but the...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

DBI::DBD::SqlEngine - Base class for DBI drivers without their own SQL engine River stage four • 984 direct dependents • 2505 total dependents

DBI::DBD::SqlEngine abstracts the usage of SQL engines from the DBD. DBD authors can concentrate on the data retrieval they want to provide. It is strongly recommended that you read DBD::File::Developers and DBD::File::Roadmap, because many of the DB...

TIMB/DBI-1.642 - 29 Oct 2018 10:43:41 GMT

13 results (0.033 seconds)