Re: [aerogear-dev] [SimplePush] pushEndpoint

Hi, here is an update for UnifiedPush (not yet working), that indicates a strategy: https://github.com/matzew/aerogear-unified-push-server/commit/dcf1c96d637... Looks like we need/should get rid of the "pushnetwork URL" on the SP Variant class and store a (SP installation) specific (simple)PushEndpoint. I know that the SP spec names it pushEndpoint, but I feel it's better to name it "simplePushEndpoint", to explicitly make sure that this is only for Installations of a SimplePushVariant. With that change we now store a lot of redundant metadata (for all the SP installations), which is most of the URL. Looking at the endpoint JSON object: { "messageType": "register", "channelID": "d9b74644-4f97-46aa-b8fa-9393985cd6cd", "status": 200, "pushEndpoint": "http://pushserver.example.org/d9b74644" } I wonder if, instead of the ENTIRE URL, we only could just store the "hash" (here "d9b74644") and continue to use the pushNetworkURL on the SP Variant (here: "http://pushserver.example.org"). HOWEVER, I think this does not work when the URL of the "request pushendpoint" server (e.g. "pushserver-foo.something.org") is different from the endpoint that receives the HTTP PUTs, from the AppServer/UnifiedPushServer. SP connect: SPClient = AeroGear.SimplePushClient({ simplePushServerURL: "http://foobar.server.com:7777/simplepush", onConnect: spConnect, onClose: spClose }); received endpoint payload: { ... "pushEndpoint" : "http://something.different.server.com/blahBlahBlub" } -Matthias On Thu, Aug 8, 2013 at 9:53 AM, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt;wrote: -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf