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.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • What you're talking about sounds a bit like the REST Architectural Style [conveyor.com]. I personally think it's a much better model for computer to computer communication than SOAP/XML-RPC, in fact I've been talking about it since way before it was even called REST (my 2001 OSCon talk about "Why SOAP Sucks", which I hope to be expanding on this year).
  • 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 rea