AeroGear Crypto Java 0.1.2 released
by Bruno Oliveira
Good morning, just to let you know we released today the bits for digital signatures and some bug fixes.
Have a happy new year sweet hearts.
--
abstractj
2 years, 6 months
UPS using JMS update
by Lukáš Fryč
Hi guys,
so as outlined in previous thread [1], I have prototyped a JMS batching
approach for push message delivery.
We've discussed the approach with Matthias, Mirek Novak and Ondrej
Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents
describes a concept that we have came with:
Diagram:
https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_...
Text Doc:
https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlz...
Implementation-wise, I've so far prototyped the messaging part (split
SenderService functionality to two subsequent queues with MDBs as shown on
diagram),
but that's just a start, since we must configure it appropriately for
efficiency (queue configuration and batch sizes) and verify that
configuration works as expected,
the prototype lives on a branch (unpolished, to be squashed later):
https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching
Off course, you can play with it already. :-)
Apart from the new requirement of using Java EE full profile (JMS), the
prototype leverages implementation-specific configurations and APIs:
- org.hibernate.Query for token streaming / batch fetching
- HornetQ configurations of queue size, blocking behavior and message
de-duplication
That pretty much binds us to WildFly/EAP - we can tweak it to run on any
compliant app server, but without specific configurations it won't work
properly.
Once configured and functionally tested (that can even wait for Beta2 I
guess),
we can cooperate with Mobile QE on testing (Stefan, Adam), their test suite
contains mocks of APNS/GCM against which we can load test.
Cheers!
~ Lukas
[1]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-re...
9 years, 1 month
Sndroid Background push notifications not working
by delalis
Hello, Aerogear is sending android push notifications properly when the app
is open (foreground) on an android device and the onNotificationGCM()
function is being called successfully when the app is open. But it is not
even putting a notification in the system notification tray when the app is
in the background or not running at all...
We are using phonegap and pushplugin on the client side and a lot of people
on google are saying that if the server is not constructing the message
payload structure properly, then Android devices will not create a
notification in the android notification tray.
Any suggestions???
here is the link I found during my research suggesting maybe Aerogear isnt
structuring message payloads properly for background notifications tray
alerts...(scroll to bottom)
http://community.phonegap.com/nitobi/topics/_pushplugin_background_notifi...
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Sndroid-Background-push-notific...
Sent from the aerogear-dev mailing list archive at Nabble.com.
9 years, 5 months
Android 2.x and cordova
by Erik Jan de Wit
Hi,
We are going to add metric support to the cordova push plugin. This
functionality was introduced in the 2.x version of the android push
lib. The android 2.x version uses 'aar' for packaging. This means the
new version can only be used with cordova android platform 4.0 as that
introduced 'aar' framework support.
Or we use a source include, we do that for the oauth2 plugin, it might
also open the option to get inclusion into phonegap build as binary
dependencies are not allowed there.
For the metrics in cordova we can make it super easy and fully
automatic all you'll have to do is add "sendMetricInfo": true in your
pushConfig:
var pushConfig = {
pushServerURL: "http://localhost:8080/ag-push",
sendMetricInfo: true,
android: {
senderID: "<senderID 123>",
variantID: "<variantID e.g. 1234456-234320>",
variantSecret: "<variantSecret e.g. 1234456-234320>"
},
ios: {
variantID: "<variantID e.g. 1234456-234320>",
variantSecret: "<variantSecret e.g. 1234456-234320>"
}
};
--
Cheers,
Erik Jan
9 years, 6 months
Versioning Documentation
by Lukáš Fryč
Hey guys,
Tadeas started a discussion about versioning documentation in the thread
[1],
and I must agree - it is a good idea to version documentation (and possibly
also guides),
especially since our UPS Console now points from the UI to the
documentation -
that is a great feature but I'm worried about maintanance of that solution,
a documentation tend to change in time, with links no longer being valid.
Lot of projects publish generated documentation separately, hosting it e.g.
on docs.jboss.org (see [2] for a sample).
I'd suggest to version both, API documentation and guides on a separated
server.
Perhaps we could version whole site?
WDYT?
Cheers,
~ Lukas
[1]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-Server...
[2] http://docs.jboss.org/richfaces/
9 years, 6 months
