--- _brian_d_foy <[EMAIL PROTECTED]> wrote: > In article > <[EMAIL PROTECTED]>, > Phil Crow <[EMAIL PROTECTED]> wrote: > > > I'm working a scheme similar to Enterprise Java > > Beans (EJB) for Perl.
> > If you like this idea I'd like to get it a > namespace > > perhaps Net::Prim. Please advise on the best > name. > > Prim stands for Perl Remote Invocation of Methods > (a > > dislexic revision of Perl RMI). > > we wouldn't put it in Net::*, but maybe (maybe) > Netx:: > > i think this should go where the other RPCish sorts > of > things go. I agree. That is where people will look. How about something like RPC::Prim? Or RPC::RIM? I'm leaning toward the later since part of the point is that you don't need to use perl to make this scheme work. > > > Prim is an xml based tcp protocol which allows you > to > > call Perl functions and methods inside a server > Perl > > interpreter from a client Perl interpreter. > > are you sure you're not reinventing the wheel? > > how does this differe from SOAP, XML-RPC, POE, and > so on? > is it just the persistence part that is different? Here are the key design principles. I think the combination is unique. 1. Objects persistent in the server without cookies 2. The web and HTTP are not involved 3. Servers can be found by peer to peer discovery 4. Any language can implement clients or servers 5. Perl servers and clients are easy to write 6. Transmitted data is mostly strings any number, any kind from client to server and back > > could you hack the persistent bit into one of the > other > frameworks? I'm looking at POE to see if it could be used instead of my scheme. If POE isn't a replacement it could be part of the solution. Phil __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
