I've once again used up an hour or so reading Stack Overflow and blog posts
on REST API versioning. (And the arguments for and against.)
Perhaps extending the discussion on how Catalyst supports REST:
https://github.com/perl-catalyst/CatalystX-Proposals-REStandContentNegotiation
I'm wondering
Bill,
Great questions and thoughts, I've inlined comment below. Sorry for the odd
formatting, yahoo email just seems to get worse and worse...
From: Bill Moseley mose...@hank.org
To: The elegant MVC web framework catalyst@lists.scsys.co.uk
Sent: Tuesday,
On Tue, Sep 17, 2013 at 10:12 AM, John Napiorkowski jjn1...@yahoo.comwrote:
People seem to get religious over how to version their API. I doubt I'd
want to take sides on this but here's how I think we could do both side
(URL version and content type versioning
Ya, I'm swayed by the Accept:
On 27 August 2013 02:07, Alex Povolotsky tark...@over.ru wrote:
In a quite simple application
[snip]
I get
[error] Caught exception in Admin::Controller::Root-index Can't use string
(Catalyst::Authentication::Store:...) as a HASH ref while strict refs in
use at accessor
