I think i would like to move the unifiedpush-node-sender,
https://github.com/aerogear/aerogear-unifiedpush-nodejs-client , to be
Currently it uses callback pattern that many node.js packages use as well
as emitting events.
When i first created this 3 years ago, that was sort of the standard way of
doing things, but Promises have become very popular(i know i love them :))
and have been a native feature since node 0.12.x
considering we have not yet hit a 1.0.0, we can pretty much just make this
change and we will be ok.
If this is to big of a change all at once, we could always do both
callbacks and Promises. I think we did this for Datamanager in the past.
Perhaps once we fully move to promises, then we can hit a 1.0.0
My only concern is other projects that might be using the sender that are
not yet on node 0.12 or above, since this is when promises became native.
I would really like to not have to include the polyfill.
i suppose those users would need to stick to the previous versions then.
anyway, would like to hear some thoughts.
thats right folks, i'm asking this question on a Friday before a Holiday
weekend(US) at 3:52(est)
i've started to implement the Device registration endpoints in node and was
just wondering what the id is here in this header
-v -H "Accept: application/json" -H "Content-type: application/json"
-H "aerogear-push-id: someid"
is it something specific, or just a random number/alpha-numeric thingy
here is the doc link for reference:
I've also decided to create this as a separate module instead of including
it in the node admin client here:
mostly becuase these registration endpoints don't needed to be KC
authenticated. and they could also be used on a IOT device or something
that runs node that has webpush/simplePush or some new crazy protocol.
while i was doing some work on the node admin client i just cretated, i was
think about this $SUBJECT and saw that the PR is still open,
I know abstractj did some awesome work around this, but i wasn't sure what
the status was.
i see it's been open for a while.
I've come back from the little vocation and ready for the work on my GSoC
What will be our plan?
I may work according to my proposal: the first steps will be the adding
WebPush support for Chrome and Firefox directly to UPS (through Google
Cloud Messaging and Mozilla Push Service).
Another way: I may begin my work from WebPush Server.
If we will begin from UPS, from which branch should I work? And for which
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
I'm trying to update the aerodoc Android cookbook example, but I can't get
the AeroDoc backend server running. Digging into the source it seems
pretty bitrotted (using picket link instead of keycloak, lucene doesn't
play nice with the wildfly docker image, dependencies are out of date, etc).
Who knows about it and can give me a hand some time?