I just created a JIRA for the node ups sender,
https://issues.jboss.org/browse/AGJS-308, that tracks the addition of using
My thoughts were to use the new features where ever possible.
Since not every feature is available on all versions of node, we would use
Babel.js https://babeljs.io/ , to transpile that code back to ES5(the
version before es6 :)).
This transpilation would happen during an "npm publish" so users would
never really see a difference.
The cool thing about Babel is that we can specify which features we want
transpiled, so in the future this list of transpiled features would
hopefully get smaller and smaller.
The latest versions of node have a lot of new features in them, so it would
be nice to start coding that way. For instance, this plugin,
https://www.npmjs.com/package/babel-preset-node5 , is a preset for the
features that node 5 has.
wanted to get some thoughts on this.
I need to implement AuthzModule to modify some of its features which i am
not getting in Oauth2AuthzModule.
Spec I want to use key/secret instead of access token.
But wanna use Authzmodule only coz then I have to feed that to pipe and
found Authz more comfortable then Auth.
If you have any example for that it will be very helpful
I've been looking trough the UnifiedPush documentation, however I can't
find an answer to my question.
I have an UPS 1.0.3 installation. When I register my application
multiple times (via install/uninstall) with GCM and UPS I'm starting to
get duplicate notifications.
According to various posts on SO
(http://stackoverflow.com/a/27073013/2853903) when an UPS sends a
notification to an re-registered device, GCM responds with a canonical
id. This canonical ID indicates that the device re-registered and all
new notifications should be routed to the new device token.
My question is: How does UPS handle this scenario?
As of version 1.0.3 it seems this case is ignored and devices keep
receiving notifications until GCM starts rejecting UPS queries.
Many thanks for your help!
In the Aerogear iOS OAuth2 library, getting an error when app enters
foreground after period of being in background. Specifically, in
TrustedPersistantOAuth2Session.swift, KeyChainWrap.read() is (very)
occasionally throwing errSecMissingEntitlement and then throwing the user
over to Safari for authentication. This is a show stopper bug for our app.
Some discussion of the topic and acknowledgement by Apple here: