OAS 4.062 Perl Cartridge Question
From: Dana Cleverdon <dana_at_ti.com>
Date: Tue, 09 Feb 1999 12:23:29 -0600
Message-ID: <36C07D20.E56D3FA9_at_ti.com>
I am trying to use the perl cartridge to manage my database connections to avoid having to waste time reconnecting to the database(s) each time my multi-page application gets called. The idea is that the perl cartridge runs an initialization script the first time it gets invoked, and that gives you a chance to do the connections just that once. It then keeps the global database handler variable around for you to reference in subsequent calls, via the perl package functionality. My problem is this:
Date: Tue, 09 Feb 1999 12:23:29 -0600
Message-ID: <36C07D20.E56D3FA9_at_ti.com>
I am trying to use the perl cartridge to manage my database connections to avoid having to waste time reconnecting to the database(s) each time my multi-page application gets called. The idea is that the perl cartridge runs an initialization script the first time it gets invoked, and that gives you a chance to do the connections just that once. It then keeps the global database handler variable around for you to reference in subsequent calls, via the perl package functionality. My problem is this:
I have a single application with multiple cartridges. All use the same
code, but call a different init script (used to connect to different
site databases). I have set the max number of instances for the
cartridges to 1, but for some reason the OAS lets different sites use
the same cartridge/server process, thus using the same database
connection. (Since the OAS just tags the second site's execution onto
the first instance, it skips the site specific init script, hence no new
connection.) Anybody ever done something like this before?
- Dana
dana_at_ti.com
p.s. OAS perl cartridge really looks like a 1.0 beta to me, anybody else feel this way? Received on Tue Feb 09 1999 - 19:23:29 CET