You
could use memcached, see Cache::Memcached on CPAN
it
works great!
Denis
Von: Peter1 Alvin [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 15. November 2005 03:11An:
modperl@perl.apache.orgBetreff: mod_perl: How pass variables
(objects) from page to page?
Please tell me I can do thi
Peter1 Alvin <[EMAIL PROTECTED]> wrote:
> Please tell me I can do this!
>
> Using mod_perl, how do you keep Perl objects in RAM from page to page?
> I don't want to re-instantiate my objects on every page request, and I
> don't want the overhead of serializing my objects to a persistent store
On Sat, 12 Nov 2005, Plymouth Rock wrote:
Before Apache::DBI installation I'd using just DBI & PgPP for
connecting with my PostgreSQL DataBase:
[ ... ]
After server's restart it couldn't to start up actually. The
error.log said the following:
[ ... ]
[Fri Nov 11 21:35:12 2005] [error] Can't
The URL
ftp://ftp.dev.ecos.de/pub/perl/session/Apache-SessionX-2.01.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GR/GRICHTER/Apache-SessionX-2.01.tar.gz
size: 12298 bytes
md5: c64ebed0b4181bb5b65b127491ccd47b
This release fixes a security problem during validation of session_i
Please tell me I can do this!
Using mod_perl, how do you keep Perl objects in RAM from page to page? I don't want to re-instantiate my objects on every page request, and I don't want the overhead of serializing my objects to a persistent store from page to page (I use A LOT of objects).
pradeep kumar wrote:
> #diff src/modules/perl/modperl_config.c
> src/modules/perl/modperl_config.c.org
> 175c175
> < modperl_config_srv_t *modperl_config_srv_new(apr_pool_t *p, server_rec *s)
> ---
>> modperl_config_srv_t *modperl_config_srv_new(apr_pool_t *p)
In the future, diff -u is much more p
Hi ,
We have very similiar problem.
Try to set-up mysql timeout per connection like this :
wait_timeout=100 ( or other suitble time for you )
interactive_timeout=100 ( or other suitble time for you )
in my.cnf
If a connection is idle more than 100 seconds mysql will kill a
connection. Next tim
On 14 Nov 2005, at 08:36, Tom Schindl wrote:I'm uncertain what you are telling here because I can use differentdatabases while connected in a connection using the1. Connect 2 DB (e.g. test)2. Query: SELECT * FROM db1.tab13. Query: SELECT * FROM db2.tab1So there's no need to move all tables into one
On Mon, 2005-11-14 at 09:36 +0100, Tom Schindl wrote:
> I'm uncertain what you are telling here because I can use different
> databases while connected in a connection using the
>
> 1. Connect 2 DB (e.g. test)
> 2. Query: SELECT * FROM db1.tab1
> 3. Query: SELECT * FROM db2.tab1
>
> So there's no
On Mon, 14 Nov 2005, Philip M. Gollucci wrote:
Leo Lapworth wrote:
Put all your virtual hosts in one database, just start the table names
differently
so instead of .tablename have
application_db._tablename
This way apache only have to connect to one database.
There may be all sorts of r
I'm uncertain what you are telling here because I can use different
databases while connected in a connection using the
1. Connect 2 DB (e.g. test)
2. Query: SELECT * FROM db1.tab1
3. Query: SELECT * FROM db2.tab1
So there's no need to move all tables into one database, simply connect
always to o
Leo Lapworth wrote:
Put all your virtual hosts in one database, just start the table names
differently
so instead of .tablename have application_db._tablename
This way apache only have to connect to one database.
There may be all sorts of reasons you don't want to do this - and from a
design
On 13 Nov 2005, at 23:46, Brett Randall wrote: Does anyone else have any ideas as to how I can utilise persistent database connections to a MySQL server via DBI, in order to speed up web queries, but without the 20 or so connections per virtual server that sit there waiting for something to happen?
13 matches
Mail list logo
