[aerogear-dev] Unified Message format (was: Re: AeroGear Push Message Format)

[Matthias Wessendorf]

On Tue, Jun 4, 2013 at 8:20 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> yes, alias/clientIdentifier "luke at force.org"



however... that assumes, that the device did register "luke at force.org" as
the "value" for the alias/clientIdentifier "metadata. (see [1] as well)

-M

[1]
https://github.com/matzew/ag-client-push-sdk/blob/master/push-sdkTests/AGDeviceRegistrationSpec.m#L58



>
>
> On Tuesday, June 4, 2013, Lucas Holmquist wrote:
>
>>
>> On Jun 4, 2013, at 11:55 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>> based on the "unification issues" (see old thread), Dan, Kris and I met
>>
>>
>> here is what we have come up with:
>>
>>
>>
>>
>>  Draft for the AeroGear Push Message Format
>>
>> The Unified Push Server allows two different ways to send message to the
>> native Push API, of the supported devices:
>>
>>    - broadcast
>>       - to all MobileVariants and their MobileVariant Instances (devices)
>>       - to one specific MobileVariant and its MobileVariant Instances
>>        (devices)
>>    - selective Send
>>
>> <https://gist.github.com/matzew/d6f1b88b85e2f6c18031#broadcast>Broadcast
>>
>> curl -v -H "Accept: application/json" -H "Content-type: application/json"
>>    -H "ag-push-application: {PushApplicationID}
>>    -H "ag-mobile-variant: {MobileVariantID}
>>    -X POST
>>    -d '{"key":"value", "alert":"HELLO!", "sound":"default", "badge":7,
>>        "simple-push":"version=123"}'
>> http://localhost:8080/ag-push/rest/sender/broadcast
>>
>> If the ag-push-application header is used, a message is send to a
>>
>> will the selective send also be able to send to 1 instance.  so send to
>> my device not yours
>>
>> Message Format
>>
>> Besides the actual payload the API accepts a few *classifiers* to select
>> a subset of registered devices.
>>  <https://gist.github.com/matzew/d6f1b88b85e2f6c18031#query-component>Query
>> component
>>
>> Currently the Server will support the following query criterias:
>>
>>    - alias: A list of email address (or usernames) to send messages to *
>>    ALL* devices of the users. Thealias needs to be stored, when the
>>    device is registering itself with the server. See here for details<https://github.com/matzew/ag-client-push-sdk/blob/master/push-sdk/AGClientDeviceInformation.h#L48-L52>
>>    - deviceType: A list of raw devices types that should receive the
>>    message (e.g. Coupon only for iPad and AndroidTablets). The deviceType needs
>>    to be stored, when the device is registering itself with the server. See
>>    here for details<https://github.com/matzew/ag-client-push-sdk/blob/master/push-sdk/AGClientDeviceInformation.h#L43-L46>
>>    . *NOTE:* For SimplePush, the deviceType is *ONLY* web. No specifics
>>    on the actual device are used due to general limitations on "user agent
>>    sniffing".
>>
>> <https://gist.github.com/matzew/d6f1b88b85e2f6c18031#message-payload>Message
>> Payload
>>
>> The message format is very simple: A generic JSON map is used to send
>> messages to Android and iOS devices. The applications on the devices will
>> receive the JSON map and are responsible for performing a lookup to read
>> values of t
>>  _______________________________________________
>>
>> aerogear-dev mailing list
>> aerogear-dev at 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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130604/533040ad/attachment.html