Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re: A RESTful API framework

by ctilmes (Priest)
on Nov 10, 2009 at 18:46 UTC ( #806313=note: print w/ replies, xml ) Need Help??


in reply to A RESTful API framework

I like some of the things that Catalyst::Controller::REST does, you might take a look at it -- it follows a similar approach to what you are proposing, but in the context of Catalyst.

In particular, it unpacks the supplied content (if you want) based on the format specified by the "Content-Type" header, and serializes your output data structure. (It uses Content-Type for that too -- I think it should use "Accept" for that.)

Your GET/PUT/POST handler doesn't have to deal with that at all, but the user can supply input in whatever format they want: XML, YAML, JSON, etc. and consume your results however they want. The perl handler can just deal with native perl data structures.


Comment on Re: A RESTful API framework
Re^2: A RESTful API framework
by jeteve (Pilgrim) on Nov 10, 2009 at 19:24 UTC
    Yep, that's interesting.

    I'm planning to allow you to plugin your own crafted Apache2::Request subclass in the system, so if you need a specific deserialization, you'd be able to implement it yourself.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://806313]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (4)
As of 2014-07-29 08:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (212 votes), past polls