—
Tadeas Kriz
tkriz(a)redhat.com
On 26 Feb 2014, at 10:33, Corinne Krych <corinnekrych(a)gmail.com> wrote:
On 26 Feb 2014, at 10:14, Christos Vasilakis <cvasilak(a)gmail.com> wrote:
> Hi everyone,
>
> we are currently working on updating our underlying networking library to rely on the
AFNetworking 2.x branch. What is more interesting of this change, is that the new library
supports the concept of ‘pluggable’ serializers, both in the request and in the response.
In other words, a plugin a can be written (and attached) to automatically convert your
object model to JSON (or XML, etc) and back, upon request/response. Although it could have
been in earlier versions, it was a pain and hacky, making the new version attractable for
this operation. Interesting enough, this spanked many projects[1][2] that take advantage
of this ability.
>
> Currently in iOS, we deal with generic dictionary objects, which although have their
flexibility, I think it will make life easier for our developers, to make use of their
object model directly during operations.
+1
This way we get closer to the AeroGear Android libs offer.
Yes, that’s something
that was extremely painful when I used AeroGear-iOS compared to Android. The marshalling
wouldn’t be difficult to implement even without the support in AFNetworking, I’ve looked
at it and it seems way easier than in Java TBH.
>
> After the AFnet 2.x merge and our 1.5 release, what do you think on creating such a
plugin and making necessary adjustments to our API?
Sound good to me.
could be great addition for 1.6
>
> Thanks,
> Christos
>
>
> [1]
https://github.com/gonzalezreal/Overcoat
> [2]
https://github.com/dcaunt/Sculptor
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev