> > Why PECL and not add it to ext/rpc? > > ext/rpc should be able to load "rpc backend" modules, or PECL is the only > sensible place to put it (especially when it's experimental!). We really > don't want to mix java, mono, xmlrpc, soap and whatnot into a single > package.
in case you don't know, there is no need for rpc backends to live inside ext/rpc nor do they have to be compiled into a single extension. rpc backends can be ordinary php extensions that register their rpc entry at the rpc extension just like they would register their class entry at the engine. so moving php-mono to pear doesn't mean that it can't be a rpc backend. the only valid reason atm is that ze2 beeing alpha, ext/rpc beeing alpha and mono beeing whatever together with sterlings bad coding style :) would result in a phreaky peace of software with totally unpredictable results. harald -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
