Re: [aerogear-dev] UnifiedPush - Time-to-live for GCM/APNs

Hello, for [1 <https://issues.jboss.org/browse/AGPUSH-110>] I'd like to propose a slight change to the message format spec ([2<http://staging.aerogear.org/docs/specs/aerogear-push-messages/> ]): The introduction of a new field, called '*ttl*', which contains a value (in seconds). This value will be translated (by the UnifiedPush Server) into the specific details of the supported platforms (GCM and APNs; NOTE: SimplePush standard does not this support this atm)... An example for a message which expires in one hour: curl -3 -u "{PushApplicationID}:{MasterSecret}" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{ "alias" : [&quot;user(a)account.com&quot;], "ttl" : 3600, // expires in one hour "message": { "alert":"URGENT CALL!!!!", "sound":"default" } }' https://SERVER:PORT/CONTEXT/rest/sender On our fluent client APIs (NodeJS and Java), I'd propose we add a timeToLive(secondsInInt) method to the APIs; Any thoughts ?

-Matthias [1] https://issues.jboss.org/browse/AGPUSH-110 [2] http://staging.aerogear.org/docs/specs/aerogear-push-messages/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev