On Sun, Jul 27, 2008 at 09:09:46AM -0700, Bill Moseley wrote:
> On Sat, Jul 26, 2008 at 06:00:39AM +0100, Matt S Trout wrote:
> >
> > sub widget :Local VersionedXMLRPC('widget.get') {
> >
> > sub widget_xmlrpc_v1 {
> >
> > have VersionedXMLRPC apply a custom a ction class that does ->can
> > bas
Bill Moseley <[EMAIL PROTECTED]> wrote on 07/28/2008 01:53:11 AM:
> On Sun, Jul 27, 2008 at 06:42:23PM -0500, [EMAIL PROTECTED] wrote:
> > > widget.1.get
> > > widget.2.get
> > > etc.
> > >
> > Icky, I think the API should be versioned -- not methods. What
if
> > the methods a
On Sun, Jul 27, 2008 at 06:42:23PM -0500, [EMAIL PROTECTED] wrote:
> > widget.1.get
> > widget.2.get
> > etc.
> >
> Icky, I think the API should be versioned -- not methods. What if
> the methods across versions are not compatible (widget1 output used with
> foo2) versioning the
Bill Moseley <[EMAIL PROTECTED]> wrote on 07/27/2008 11:09:46 AM:
> On Sat, Jul 26, 2008 at 06:00:39AM +0100, Matt S Trout wrote:
> >
> > sub widget :Local VersionedXMLRPC('widget.get') {
> >
> > sub widget_xmlrpc_v1 {
> >
> > have VersionedXMLRPC apply a custom a ction class that does ->can
> > b
Bill Moseley schrieb:
I'm looking for suggestions how to best support multiple API versions
in an application.
The API and web share many controller actions. As is not uncommon,
actions available for the API are defined with an attribute:
sub foo : Local XMLRPC( 'foo.get' ) {
This is grea
On Sat, Jul 26, 2008 at 06:00:39AM +0100, Matt S Trout wrote:
>
> sub widget :Local VersionedXMLRPC('widget.get') {
>
> sub widget_xmlrpc_v1 {
>
> have VersionedXMLRPC apply a custom a ction class that does ->can
> based dispatch, same way Catalyst::Action::REST does.
C::Action::REST uses "Acti
On Fri, Jul 25, 2008 at 07:09:58AM -0700, Bill Moseley wrote:
>
> I'm looking for suggestions how to best support multiple API versions
> in an application.
>
> The API and web share many controller actions. As is not uncommon,
> actions available for the API are defined with an attribute:
>
>
I'm looking for suggestions how to best support multiple API versions
in an application.
The API and web share many controller actions. As is not uncommon,
actions available for the API are defined with an attribute:
sub foo : Local XMLRPC( 'foo.get' ) {
This is great for sharing code as o
