Re: Re: (New || Old) idea?

--- Stig Bakken <Stig.Bakken@fast.no> wrote: > 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. That would be interesting, and an idea I've been toying with for some time. As the standard is at the moment, you cannot do this type of object proxying directly. I would envision that it might be feasible to send an object or class definition serialized (xmlrpc_base64 encoded perhaps), and then reconstructed at the other end, instantiated, etc. > 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 ;-) Another issue is that of resource discovery. For example, I need an object of type FOO and want to execute methods of it, but I do not know where to find it. AFAICT the simplest solution now would be to have a lookup server to query, perhaps one using the JINI interfaces and protocol. One of the cool things about JINI is that the JINI lookup service ships a proxy object back to your application, which handles the calling of the remote resource for you. Had not played w/ the Java-PHP extension for awhile, but this is something the could be feasible using that. Just my 2 cents. ===== --- Jesus M. Castagnetto (jcastagnetto@yahoo.com) __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/?.refer=text