<div dir="ltr">Hi,<div><br></div><div>in the message spec discussions, a while ago, we agreed that for "triggering" notifications for registered SimplePush clients, the "deviceType" needs to match "web" (see [1] for the spec).</div>
<div><br></div><div>Right now, only a few "metadata" items are submitted to the UnifiedPush Server, using the "registerWithPushServer" (perhaps we should rename it ?):</div><div><a href="https://github.com/aerogear/aerogear-js/blob/Notifier/src/unified-push/aerogear.unifiedpush.js#L48-L52">https://github.com/aerogear/aerogear-js/blob/Notifier/src/unified-push/aerogear.unifiedpush.js#L48-L52</a><br>
</div><div><br></div><div>However, I have already filed a ticket for that (see [2]), since on Cordova (and similar things) a bit more "metadata" would be nice (since they are really treated as "native" clients, with APNs/GCM setup on the UP server etc)</div>
<div><br></div><div><br></div><div>Now... talking about metadata (including the "deviceType"). The above statement, that the "deviceType" needs to match "web" for SimplePush clients leads to a question:</div>
<div><br></div><div>* Do we want to have ALL SimplePush clients auto-submit the "deviceType":"web", or not ? <br></div><div><br></div><div>If NOT, I guess that means there will be NO deviceType for SimplePush clients, on the UnifiedPush server, which is fine.</div>
<div><br></div><div>But once more metadata is possible (e.g. after AGJS-56), I think we than need to ensure that a SP client does not set it's deviceType to something like "winBROwsPhone" :)</div><div><br></div>
<div><br></div><div>-Matthias</div><div><br></div><div><br></div><div>[1] <a href="https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-push-messages/index.markdown#query-component">https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-push-messages/index.markdown#query-component</a><br clear="all">
<div>[2] <a href="https://issues.jboss.org/browse/AGJS-56">https://issues.jboss.org/browse/AGJS-56</a></div><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>