Thanks Marius for the detailed proposal. I personally prefer the granular one as it's more resource oriented, which makes more sense in my opinion for an HTTP API (be it REST or not) and that was in fact the rationale that drove the current design. Also the flatten design looks ok, however having to make two API calls to get the status of a certain replication doesn't sound too nice to me. However I would go for either the granular one or the flatten one, not a mixture of them.
Regards, Tommaso 2014-02-13 15:12 GMT+01:00 Marius Petria <[email protected]>: > Hi, > > I have placed the proposal to [1]. > > Thanks, > Marius > > [1] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=38572805 > > > > -----Original Message----- > > From: Marius Petria [mailto:[email protected]] > > Sent: Wednesday, February 12, 2014 4:59 PM > > To: [email protected] > > Subject: RE: Replication REST-ful/HTTP API > > > > I will do that. > > > > Thanks, > > Marius > > > > > -----Original Message----- > > > From: Felix Meschberger [mailto:[email protected]] > > > Sent: Wednesday, February 12, 2014 12:56 PM > > > To: [email protected] > > > Subject: Replication REST-ful/HTTP API > > > > > > Hi > > > > > > There are at least two Sling issues currently discussing REST-ful (or > > > HTTP) API approaches for the new replication module: SLING-3385 [1] > > > and SLING-3352 [2]., > > > > > > Instead of independently find and discuss solutions, I would prefer to > > > see a complete picture proposal for such APIs. How about you, @Marius, > > > creating some proposal on the Sling Wiki (as a child to [3]) that we > > > can further discuss and then implement ? > > > > > > Thanks > > > Felix > > > > > > [1] https://issues.apache.org/jira/browse/SLING-3385 > > > [2] https://issues.apache.org/jira/browse/SLING-3352 > > > [3] > > > https://cwiki.apache.org/confluence/display/SLING/Concepts+and+Ideas >
