<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML DIR=ltr><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"></HEAD><BODY><DIV><FONT face='Arial' color=#000000 size=2>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Once again I have the need to
announce a quick bugfix release.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr>List member Xing reported that under heavy load his server appeared
to be leaking connections when using the persistent interface to php
mcache. It turned out that<FONT face=Arial size=2> when creating a
persistent object I had a slight bug in the generation of the internally unique
identifier for the object such that even if the php code passed the same unique
id, it would not always end up generating the same internal id, and as such you
could end up creating new persistent connections when one that matched your
request already existed. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I have updated the website <A
href="http://www.klir.com/~johnm/php-mcache/">http://www.klir.com/~johnm/php-mcache/</A>
with version 1.1.2 which fixes this bug. Anyone who is using the extension
along with persistent connections is urged to update. There is no impact
to those who are using standard non persistent connections.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial
size=2>John</FONT></DIV></FONT></DIV></BODY></HTML>