In article <[EMAIL PROTECTED]>, Phil Crow <[EMAIL PROTECTED]> wrote:
> --- _brian_d_foy <[EMAIL PROTECTED]> wrote: > <[EMAIL PROTECTED]>, > > Phil Crow <[EMAIL PROTECTED]> wrote: > > > I'm working a scheme similar to Enterprise Java > > > Beans (EJB) for Perl. > > 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? can the second level be something more descriptive? "RIM" stands for Remote Invocation of Methods, but "RPC" already has "Remote" in it. i'm not an RPC sort of guy, so i don't have a good suggestion, but i'd like to see something explicit rather than initials. maybe something like: RPC::Method::* RPC::Method::Server RPC::Method::Client RPC::Method::Invoke but Method is ambiguous. it doesn't mean the way you do it, but that it is a subroutine. -- brian d foy (one of many PAUSE admins), http://pause.perl.org please send all messages back to [EMAIL PROTECTED]
