Re: (New || Old) idea?

From: Date: Mon, 02 Apr 2001 06:35:03 +0000
Subject: Re: (New || Old) idea?
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-144@lists.php.net to get a copy of this message
On Sun, 1 Apr 2001, Jon Bardin wrote: > I want to start a new project/company of sorts. What this > project/company intends to offer to the opensource community is a free > XMLRPC server with tons of functions allready available for clients to > connect to and use. this is what brings me to PEAR... it being IMHO > the most complete and well orginized collection of usefull PHP classes > that I can come across. As of now I have only minimal code written so > far... been busy trying to think of planning and all of that.. But > what I think would be neccasary on my part is an effecient way if > interfaceing with the PEAR archive to allow drop in code. i.e. whenver > PEAR gets updated the code on my server will get updated etc etc.. I > feel it would be pointless for me to try nd replicate what has > allready been done. I am not here to reinvent the wheel... I just want > to provide a means for everyone to use this wheel and to use it for > free. I am posting this to hear to see what everyone on this side > feels about my idea... please respond with your > comments/suggestions/ideas I will looking forward to hearing them. (Cc'ed to pear-dev instead of pear-general) Hi, What I would really like to see is an object proxying mechanism using XML-RPC, for any PEAR class. By proxying I mean that you can make a local instance of an object that really is on a remote server, and that all method calls and variable accesses go through XML-RPC. Example: <?php $robj = new Object_Proxy("http://somesite/path", "new Some_Class"); $robj->this_method_is_proxied_to_another_machine(); ?> It may be that XML-RPC or HTTP in general is not the ideal solution though. First of all, it requires one HTTP request per method call. You also cannot refer an object you just created in a subsequent call, because the subsequent call will be a new request, and you don't have a syntax for referring to the object. The latter could be implemented though, but then we'd need "persistent XML-RPC" connections. Since XML-RPC is specified to be used over HTTP, it wouldn't be XML-RPC anymore. CORBA anyone? (just kidding ;-) - Stig

« previous php.pear.dev (#144) next »