On Tue, 11 Jul 2000 15:10:25 -0600 (MDT), rise wrote:
>On Tue, 11 Jul 2000, Mike Miller wrote:
>> Not good for heavy use, but for the 3-4 times a month
>> it gets used in production, it works perfectly okay.
>
>There is one significant issue with using DBD::Proxy / DBI::ProxyServer on
>Windows: lack of fork. If you're going to be using it you probably want to
>either use 5.6 (problem mostly solved) or start several proxies on
>differenct ports. Check the PlRPC & Net::Daemon docs for informations
>about forking. This is mainly annoying because only one connection can use
>the single process proxy at once. Otherwise we've seen no problems with
>using it as production method to slurp data from an Access DB into a
>RRDBMS (Real Relational Database Management System tm).
>
Thanks for the info. I've never hit this because the only process that uses the proxy
is initiate from
a cron job (on a unix box) that runs every hour looking for updates in the access db
(which gets updated
3-4 times a month, if that <grin>). It is also the only task that ever uses the
proxy, so of course I'd
never see it.
For me the entire entire thing was a hack, but what the hey, it works ... <grin>
Brgds,
Mike.
