Hello Vivek, thanks for the interest in our project On Wed, Feb 19, 2014 at 11:34 AM, Vivek Pandey <vivek.pandey(a)pinelabs.com&gt;wrote: > Hello, > > > > While going through the aerogear-server-push documentation , I could not > find an example where we can send a push message using "id" returned by > adding a new device token at /rest/registry/device. > > > > Is there a plan to add such a support ? > We have a ticket for that: https://issues.jboss.org/browse/AGPUSH-420 but we did not do it, ATM, as this is hard to do for the supported SimplePush bits (e.g. for FirefoxOS). We thought about using the device token (e.g. from APNs or the registrationID from GCM), but w/ SimplePush / Mozilla's FirefoxOS this is really an URI. However, you raised a great point, each installation gets an ID in our database - perhaps we could use that. But that means "your application" needs to store our ID somewhere (in addition to GCM/APNs IDs and Mozilla's Push URI). But I do like the ideas > Is relying on unique "alias" a good option to implement the requirement > of identifying a device uniquely ? >

> > Thanks > > Vivek > > ------------------------------ > This message may contain privileged and confidential information and is > solely for the use of intended recipient. The views expressed in this email > are those of the sender and not of Pine Labs. The recipient should check > this email and attachments for the presence of viruses / malwares etc. Pine > Labs accepts no liability for any damage caused by any virus transmitted by > this email. Pine Labs may monitor and record all emails. > ------------------------------ > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)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