Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

SOAP, XML & RPC - some thoughts More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Interesting (Score:1)

by djberg96 (2603) on 2002.03.04 8:55 (#5424) Journal

Thanks for the link. What I'm planning will be even *more* flexible than simple interface genericity (at least as I understand it). There won't necessarily need to be an interface - the server will simply do what the client tells it to do (danger - "rm *" - danger). You won't have to know the methods - you can *make* the methods on the fly.
I should say, there will at least be an *option* to set up the server that way. In a secure intranet (i.e. no outside access), I don't see this as a problem. I realize this could be a loaded gun in the hands of a child programmer, so I'll have to plan out how I want to approach the security aspect.
I just need some *time* to actually get started on all this, including time to play with Net::Server which looks like it will be a great base class. Maybe I'll call it Net::Server::RPC if he'll let me.

Reply to This

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.