Req #53594 [Fbk->Tbd]: php-snmp rewrite

Edit report at http://bugs.php.net/bug.php?id=53594&edit=1 ID: 53594 Updated by: lytboris@php.net Reported by: lytboris at gmail dot com Summary: php-snmp rewrite -Status: Feedback +Status: To be documented Type: Feature/Change Request Package: SNMP related Operating System: irrelevant PHP Version: trunk -Assigned To: +Assigned To: lytboris Block user comment: N Private report: N New Comment: OO API should be documented from scratch as most of old API functions Previous Comments: ------------------------------------------------------------------------ [2011-01-31 12:41:36] lytboris@php.net Automatic comment from SVN on behalf of lytboris Revision: http://svn.php.net/viewvc/?view=revision&revision=307877 Log: Improved SNMP extension. FR #53594 ------------------------------------------------------------------------ [2011-01-05 19:04:56] lytboris at gmail dot com Introducing full-featured OO API. It covers bug #46065 also. Old API *_set_* functions actually sets `global' preferences, they are used when creating new object instance. $object->... properties are used object(session)-wise. ------------------------------------------------------------------------ [2010-12-31 19:52:07] lytboris at gmail dot com OK. There will be full-featured OO API without adding new functions into legacy API (e.g. no session support). Though old functions will be provided with two features (in sake of code cimplicity): * multi-OID * strict output typing ------------------------------------------------------------------------ [2010-12-29 18:22:55] pajoye@php.net No need to deprecate it, but tell anyone asking for a feature for the legacy API to migrate to the new shiny one :) ------------------------------------------------------------------------ [2010-12-29 18:21:57] pajoye@php.net It is much easier and cleaner to simply go straight to OO then, without procedural API, and keep the old for legacy apps. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/bug.php?id=53594 -- Edit this bug report at http://bugs.php.net/bug.php?id=53594&edit=1