First off, big kudos and ++ to you for actually implementing a REST plugin! I know there's been talk on and off about this, both on the cgiapp mailinglist and in #cgiapp, and it's very exciting to finally have something real.

I do have the feeling that the REST_route setup calls are a bit verbose. Would it be possible to come up with a terser interface?

Maybe something like this:

$self->REST_route(
    widgets => {
        GET  => { MEDIA_TYPES => [...], FUNCTION => [...] },
        POST => { ... },
    },
    some_other_runmode => {
        GET  => { ... },
        POST => { ... },
    },
);
[download]

That avoids typing out the obvious for every single runmode/request_method combination.

Another idea is to configure the REST details with attributes on the actual functions. That might look like this:

# nothing in setup()

sub get_widget : REST( 
                         GET    => widgets,
                         TYPES  => [ 'application/xhtml+xml', 'text/ht
+ml', 'text/plain' ],
                         PARAMS => [ 'product_number' ]
                     )
{
    # implementation
}
[download]

That might be a bit heavy though, and it may not be too practical. But the obvious benefit is that you keep the REST details close to the function handling the request, and there is minimal redundancy.

Anyway, this is in no way meant to detract from the excellent work you did here. These ideas just popped up on first reading, and I didn't think them through. Take them for what they're worth :-)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.