A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Waterfall_Cache has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 47

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 194

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Memcache_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 275

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; Filesystem_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 440

A PHP Error was encountered

Severity: 8192

Message: Methods with the same name as their class will not be constructors in a future version of PHP; APC_Cache_System has a deprecated constructor

Filename: _common/waterfall_cache.php

Line Number: 628

[ANNOUNCE] Apache::Session 1.52

[ANNOUNCE] Apache::Session 1.52

By Kevin Reichard (Send Email)
Posted Jul 25, 2000


Download the authoritative guide: Data Center Guide: Optimizing Your Data Center Strategy

Download the authoritative guide: Cloud Computing: Using the Cloud for Competitive Advantage

Apache::Session 1.52 has been uploaded to CPAN. The main change in this version is the inclusion of modules to work with Sybase, contributed by Chris Winters, and a smattering of bugfixes. Apache::Session 1.52 has been uploaded to CPAN. The main change in this version is the inclusion of modules to work with Sybase, contributed by Chris Winters, and a smattering of bugfixes.

There is a memory leak if you use a persistent database handle with Apache::Session. The memory leak is in DBI, and I haven't had a chance to fix it yet. You can minimize the impact of the leak by occassionally letting your Apache children die, or re-opening your database connections.

Get the new Apache::Session here: http://www.perl.com/CPAN/modules/by-authors/Jeffrey_Baker/

Page 1 of 1

Thanks for your registration, follow us on our social networks to keep up-to-date