by kamermans » Thu Sep 09, 2010 1:25 pm
Interesting. I have noticed this error when doing regression testing where over 60,000 user agents are tested as fast as possible.
I'll definitely include the destructor in version 2.1.3 (to be released soon). As far as MySQL::kill() is concerned, there are conflicting comments, one poster says "You should always use mysqli_kill() function before mysqli_close() to actually close and free up the tcp socket" while another (under MySQL::kill) says "Be careful using this before mysqli::close. Killing the thread before actually closing the connection will leave the connection open". As you suggested, I will not use the kill() method.
For users with PHP >= 5.3.0, Tera-WURFL will default to a persistent MySQLi connection, the connection will be reused.
I think I'll put the destructor on the DB Connector as opposed to the TeraWurfl class, but I'm not quite sure yet...
Thanks,
Steve Kamerman
Tera-WURFL Author
COO of ScientiaMobile
IMPORTANT ANNOUNCEMENT! Tera-WURFL and WURFL have joined forces! We have launched
ScientiaMobile to provide
commercial support for our device detection solutions.
Tera-WURFL.com |
Device Explorer