Re: [aerogear-dev] iOS API overhaul - remove method
On Thu, Dec 20, 2012 at 2:16 PM, Christos Vasilakis <cvasilak(a)gmail.com> wrote:
Hi team,
as part of the API overhaul ticket[1] for the next CR1 release, we are suggesting that
in the 'remove' method in the Pipe object, we should pass the actual object rather
than the id. That is, because of >iOS familiarity (CoreData) , users expect a remove
to happen on an object [2] rather than the id of the object.
Even that JPA thing :) does it like that:
http://docs.oracle.com/javaee/5/api/javax/persistence/EntityManager.html#...
We can determine the final endpoint by using the "recordId"
property of the config object in iOS and the "RecordId annotation" in Android as
we currently do on save. In Javascript it support both
approaches (either by id or by object).
sounds good!
But irrelevant for the actual API, since that is an implementation detail ;-)
What do you think?
+1 on using the 'object', instead of an the recordId
-M
A ticket has been already opened for this change, see [3]
Thanks,
Christos
[1] https://issues.jboss.org/browse/AEROGEAR-763
[2]
https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/C...
[3] https://issues.jboss.org/browse/AEROGEAR-758
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf