when we share the AG Sec. code - we need to pass in a concrete impl of the http client: https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/AeroGea... So for the CoreDataPlugin, we need to change that, since there is no common "interface", see https://github.com/matzew/aerogear-store-ios/blob/security/AeroGear-Store... -M On Thu, Dec 13, 2012 at 12:19 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Hello, > > the CoreData plugin has its own HTTP client (since it's inheriting > from AFIncrementalStore API), but the "public" API of that own client > is similar to the one used on the Pipe IMPL: > > + (AGIncrementalStoreHttpClient *)clientFor:(NSURL *)baseURL; > > versus > > + (AGHttpClient *)clientFor:(NSURL *)url; > > Technically both HttpClients are extensions of the AFNetworking > HTTPClient. In order to reuse the same public API for different http > clients, I thought we could introduce a (public) protocol that allow > it to write type-safe HTTP clients. > > Any thoughts? > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Dec 13, 2012, at 9:19 AM, Matthias Wessendorf wrote: > Hello, > > the CoreData plugin has its own HTTP client (since it's inheriting > from AFIncrementalStore API), but the "public" API of that own client > is similar to the one used on the Pipe IMPL: > > + (AGIncrementalStoreHttpClient *)clientFor:(NSURL *)baseURL; > > versus > > + (AGHttpClient *)clientFor:(NSURL *)url; > > Technically both HttpClients are extensions of the AFNetworking > HTTPClient. In order to reuse the same public API for different http > clients, I thought we could introduce a (public) protocol that allow > it to write type-safe HTTP clients. What would we gain from this apart of unifying the usage?

Is there something else I'm not seeing?

> > Any thoughts? > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- qmx _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev