On Tuesday, April 23, 2013, Summers Pittman wrote:
On Tue 23 Apr 2013 04:21:12 AM EDT, Matthias Wessendorf wrote:
> Summers,
>
> for GCM/Android, I guess we could deliver a "utility" Intent, that
> folks just need to plugin.
> Not sure if we also could offer something for the manifest;
>
There is tooling which may be the easiest. Right now I don't think
there is an easy hit this button and slurp the config from my library
project which will make it only plug and play.
Thanks!
> -M
>
>
>
> On Mon, Apr 22, 2013 at 11:33 AM, Christos Vasilakis
> <cvasilak@gmail.com <mailto:cvasilak@gmail.com>> wrote:
>
> On Apr 22, 2013, at 11:33 AM, Matthias Wessendorf
> <matzew@apache.org <mailto:matzew@apache.org>> wrote:
>
>> Hi,
>>
>> Christos and I sync'd up on getting code ready for a client SDK,
>> that supports registration of a device, with our backend (e.g.
>> Push/Connectivity Server)
>>
>> A few general notes:
>>
>> * We should have Reachability in mind:
>> https://www.pushlayer.com/blog/2013/03/12/ios-push-notifications-best-practices)
>
> +1 for that (and actually during submission of an app to the
> store, if 'Reachability
> <http://developer.apple.com/library/ios/#samplecode/Reachability/Introduction/Intro.html>'
> is not enforced the app is rejected by apple). This is to ensure
> good practice and the user of the app is informed by a dialog that
> the app can't work if the net connection is down.
>
>>
>> * Registration of the device is the main issue/focus of the
>> (Push Registration) SDK:
>> https://github.com/matzew/ag-up-poc#registration-of-an-installation-on-a-device-ios
>>
>> = Requirements =
>> The API should be able to send these items to the device
>> registration server:
>> * token
>> * os
>> * type
>> * version (of the OS)
>> * alias/client-identifier (optional)
>
> +1 looks fine, the minimum required for the reg to work in the
> backend.
>
>>
>> Right now (see above github link) APP also needs to know these IDs:
>> - push app id
>> - mobile variation id
>>
>> (and the URL of the Push Server)
>>
>>
>> greetings,
>> matthias
>>
>
> Thanks
> Christos
>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org <mailto:aerogear-dev@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
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev@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