i remember there was a "readme" that showed the different endpoints on the
UPS and what they expected for payload(on POST, PUT) and what they
returned(format, http status codes)
i can't seem to find it now, it's possible that it is really out of date,
but i was randomly doing something that this might have helped with
I just noticed (working on the doc) that when clicking through the wizard,
I can only add one variant
Now, I am wondering if we should update the wizard, so that I can also add
another vairant, inside of the wizard ?
Or is that something we have done on design? That we just want just one
variant to be created on the wizard - and for a second (and third, etc)
variant, the user must go to the puah-app and add it there ?
Because we have a critical issue with the current push plugin we
are going to release the new plugin that adds support for sending
metrics and uses the new android 2.0 libs you can test it by using the
currently we have the UPS server _and_ the SimplePush server on on
Since the UPS now is a full profile dependent server (JMS/HornetQ) is on,
I'd like to change remove the SimplePush Server from the cartridge.
For SimplePush, IMO it's best to have a standalone cartridge, that just is
Java based and fire up the Netty based server - no WildFly really needed,
just MySQL and the SimplePush server
Sooooo we have a 2.2.0 staged. Google has a ton of new functionality
rolling out for GCM.
We think that 2.2.0 works with it mostly correctly but we are finding some
"gotchas". Notably it looks like Google is sending some ACK messages after
we register that the library is ignoring.
We will need to support InstanceID (tl;dr; Google is enhancing
registraiton_id). Passos and I are still digesting the volumes of stuff
being rolled out from IO so we can't really give too many details right now
because we simply don't know them (And Google is still updating their docs,
fixing links, etc).
So the question to the list is :
Do we delay 2.2.0 and include support for InstanceID and any other best
practices Google has introduced or do we release 2.2.0, document / work
around any gotchas and then prioritize GCM 3.0 support for 2.3.0?