• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Mojolicious and REST
 

Mojolicious and REST

on

  • 1,052 views

Lessons learning from implementing a RESTful interface using Mojolicious

Lessons learning from implementing a RESTful interface using Mojolicious

Statistics

Views

Total Views
1,052
Views on SlideShare
1,051
Embed Views
1

Actions

Likes
3
Downloads
5
Comments
1

1 Embed 1

http://lanyrd.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Mojolicious and REST Mojolicious and REST Presentation Transcript

    • Mojolicious and REST Building a RESTful interface using Mojolicious By @jonasbn for Nordic Perl Workshop 2013
    • - $authbridge->route(‘/domain/is_available/:domainname') + $authbridge->route(‘/domain/is_available/#domainname')
    • • Implementing REST using Mojolicious is easy • very easy • too easy
    • but!
    • Rest in Practice Ian Robinson, Jim Webber and Savas Parastatides • On mediatypes, describes an antipattern implemented in Ruby on Rails
    • • • • On mediatypes, describes an anti-pattern implemented in Ruby on Rails (RoR) This pattern has unfortunately made it to Mojolicious and that is to have the mediatype communicated on the URL
    • so?
    • • The recommended practice is to use Accept headers to communicate media-types • and these can be weighted 8-o • We use HTTP status codes to communicate state and status • URLs should be used to communicate intent not formatting • For Mojolicious this required some experimenting
    • code?
    • $self->respond_to( json => { status => $status, json => $response }, text => { status => $status, text => $message }, xml => { status => $status, text => XMLout( $response, NoAttr => TRUE, RootName => XML_ROOT, keyattr => [], XMLDecl => XML_DECL ) }, any => { status => HTTP_UNSUPPORTED_MEDIA_TYPE, json => status_message(HTTP_UNSUPPORTED_MEDIA_TYPE) }, );
    • Lessons Learned • Mojolicious does the right thing when it comes to the Accept header and actually does it quite well • The anti-pattern supported by Mojolicious can be avoided • Use # instead of : in your routes (see the diff) and it will work • But actually ?format=(json|text|xml) is supported but we only use it for debugging (and it actually has precedence (and it is undocumented on our side))