Re: [cgiapp] Re: RFC: CAP::Plugin::PathInfo

[Timothy Appnel <suppressed>]

On 7/12/05, David Emery <suppressed> wrote:

> Q: I had the impression from your REST post that DELETE and PUT were
> unusable from a practical POV. Are you actually able to use those in
> real life?

It's still useful in non-browser systems like a web service API gateway. 
 
> It seems to me (from what I understand of it so far) that
> implementation of REST varies a lot from case to case. I've yet to
> clearly see a lowest common denominator beyond wanting all of: request
> method, POST and GET data,  path info - and being able to tell which
> is which in order to handle each appropriately. And from that point
> the disagreement starts. 

Yeah, I suppose you could drive yourself crazy with all of the URL
tricks you could use. Perhaps saying is has to be in the path info for
CGI::App's purpose is fine.

> Do you think it's worth while trying to go
> beyond that in this plugin?

Not entirely sure. My instinct is all that is needed for now is a
handler to register run modes based on some path_info prefix and HTTP
request method and an associate to evaluate which method to execute. I
don't think breaking the pathinfo up into pieces is that helpful
because it will vary on the implementation. It's also not that hard to
do -- probably a second split call should do it.

<tim/>
-- 
Timothy Appnel
http://www.timaoutloud.org/

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed