Re: Is REST best?

Building up your application with a separation between a RESTful service API and one of many potential clients using a JS web frontend is a great idea.

There are many ways to get started quickly, but I would recommend Dancer or if you're constrained to a CGI environment, using CGI::Application with CGI::Application::Dispatch. Others here will have similar and equally valid suggestions.

Comment on Re: Is REST best?

Replies are listed 'Best First'.
Re^2: Is REST best? by boftx (Deacon) on Jul 11, 2014 at 21:42 UTC
I concur with perlfan, but I suggest looking at Dancer2 instead of Dancer based on what was being said by some notable personages at YAPCNA:2014. Note, I haven't had occasion to play with it yet, this is based solely on various discussions held mainly during the after-hours booze sessions. (perlfan was a part of some of them, but can be forgiven if he does not have a complete recollection of them. :) ) You must always remember that the primary goal is to *drain the swamp* even when you are hip-deep in alligators.	[reply]

Replies are listed 'Best First'.

Re^2: Is REST best?
by boftx (Deacon) on Jul 11, 2014 at 21:42 UTC

I concur with perlfan, but I suggest looking at Dancer2 instead of Dancer based on what was being said by some notable personages at YAPCNA:2014. Note, I haven't had occasion to play with it yet, this is based solely on various discussions held mainly during the after-hours booze sessions. (perlfan was a part of some of them, but can be forgiven if he does not have a complete recollection of them. :) )

You must always remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

[reply]