Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14109 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75186 invoked by uid 1010); 17 Dec 2004 17:07:44 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 59489 invoked from network); 17 Dec 2004 17:03:58 -0000 Received: from unknown (HELO mail.brokerbin.com) (216.17.25.70) by pb1.pair.com with SMTP; 17 Dec 2004 17:03:58 -0000 Received: from [10.0.0.254] (unknown [209.180.50.185]) by mail.brokerbin.com (Postfix) with ESMTP id 363674FC04D for ; Fri, 17 Dec 2004 11:03:58 -0600 (CST) Message-ID: <41C3110D.5070101@cyberlot.net> Date: Fri, 17 Dec 2004 11:02:05 -0600 User-Agent: Mozilla Thunderbird 0.7 (X11/20040615) X-Accept-Language: en-us, en MIME-Version: 1.0 To: internals@lists.php.net Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: session_set_save_handler From: lists@cyberlot.net (Richard Thomas) Right now the only way to change the serialize_handler is through php.ini or ini_set. Would it not make sense to have this part of session_set_save_hanlder and allow people to register there own functions or even no function at all for this? One usefull example of this, someone using a database to session information might want to store and update session variables 1 at a time to reduce the amount of data passed around in large sessions. At this time the only way to do that is to unserialize the data on writes and serialize the data on reads manually. -- Richard Thomas - CEO Cyberlot Technologies Group Inc. 507.398.4124 - Voice