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
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Something about roses and names (Score:1)
Just take the ideas you like about REST, build your API as you see fit and call it something else. POX/HTTP, or whatever.
Re: (Score:1)
As long as you understand what you lose by giving up constraints imposed by REST [plasmasturm.org], that’s perfectly fine.
Re: (Score:2)
AFAICT, I like everything about REST but the "start at the root and discover" rule. The rest of it, including what Roy said in his original blog post about using document types vs documenting "parameters, seems very sane.
But for me, non-interactive clients are the key target of a web-based API. I think browsers do an acceptable job of providing an interactive client already.
Re:Something about roses and names (Score:1)
What I said stands: if you understand what you lose by giving up that rule (a lot – much more than naïvely obvious), go ahead and give it up.
Reply to This
Parent