Hi Asger, Thanks for putting this together! I agree with the principles but I haven't given it a deep read.
My initial reaction (and this isn't a criticism) is that the return needs to be more tightly specified. E.g. the http status codes, the relevant headers, and the returned entity (if applicable). What do you think? Elliot On Oct 27, 2009, at 1:39 PM, Asger Askov Blekinge wrote: > Hi Guys > > I created a wiki page with my proposal. > http://fedora-commons.org/confluence/display/DEV/Alternative+REST+API > > I would appreciate it, if you would give it a look, and tell me what > you > think of the idea? > > Regards > > On Tue, 2009-10-27 at 17:02 +0100, Peter Cliff wrote: >> Surely the best thing to do would have two methods: >> >> GET /createNew & >> GET /createExisting/{pid} >> >> ;-) >> >> (I'm joking!!) >> >> Pete Cliff >> OULS >> >> On Tue, 2009-10-27 at 10:32 -0400, Elliot Metsger wrote: >>> On Oct 27, 2009, at 10:27 AM, Schwichtenberg, Frank wrote:\ >>>> If the PID is previously known and can be included in the URL (/ >>>> objects/{pid}) I would say definitely PUT. In case of create >>>> without >>>> PID I would agree with POST but would send it to /objects. >>>> Appended with create seems to mean calling the create-method. >>> >>> I agree with Frank and David on just using /objects... no need for >>> "create" >>> >>> ------------------------------------------------------------------------------ >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >>> is the only developer event you need to attend this year. >>> Jumpstart your >>> developing skills, take BlackBerry mobile applications to market >>> and stay >>> ahead of the curve. Join us from November 9 - 12, 2009. Register >>> now! >>> http://p.sf.net/sfu/devconference >>> _______________________________________________ >>> Fedora-commons-developers mailing list >>> Fedora-commons-developers@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart >> your >> developing skills, take BlackBerry mobile applications to market >> and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> Fedora-commons-developers mailing list >> Fedora-commons-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/fedora-commons- >> developers > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Fedora-commons-developers mailing list Fedora-commons-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
