Asger, Is this proposal intended to enhance the current "REST" API, or is it intended to replace it? I would like to know if I should be looking at this proposal with the perspective that it is complete, or with the perspective that it exists alongside the other APIs. In particular, if I have a use case that this API is unable to address (but the existing REST or API-A/M could address), should I identify that as a potential problem?
-Aaron On Tue, 2009-10-27 at 18:39 +0100, 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? > ------------------------------------------------------------------------------ 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
