[aerogear-dev] iOS API cookbook examples

[Daniel Bevenius]

Nice work!

Was wondering about this sentence:
Paging metadata located in the server response (either in the headers, in
the body or using [webLinking <http://tools.ietf.org/html/rfc5988> are used
to identify the next or the previous result set.
Could that perhaps be changed to something like (either in the headers by
webLinking or custom headers, or in the body).

I noticed a few character that are not being represented properly:
A Pipeline object represents a ‘collection’ of server connections (aka
Pipes).
The class offers simple APIs to add, remove or get access to a ‘data
store’
The class offers simple APIs to add, remove, or get access to a
‘authentication module’.

/Dan



On 18 March 2013 09:11, Christos Vasilakis <cvasilak at gmail.com> wrote:

> Hi,
>
> for the needs of [1] we created a page that collectively has code examples
> for all the different subsystems available in iOS.  Much of the content
> used to reside in API.md [2], but now that we have moved it inside the API
> documentation, we though it would be better instead of removing the file
> completely, to convert it to a web page that will be hosted on our web site.
>
> I have converted to asciidoc and added some more content for the basic
> concept of the available iOS subsystems. The result can be found here [3]
>
> Wdyt?
>
> Thanks
> Christos
>
> [1] https://issues.jboss.org/browse/AEROGEAR-1007
> [2] https://github.com/aerogear/aerogear-ios/blob/master/API.md
> [3] http://tinyurl.com/cnvb6e6
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130318/75e7fc4d/attachment.html