AGAuthenticationModule was originally made to login/logout/register with
the AeroGear controller. Since controller is dead in a ditch somewhere,
for AGDroid 2.0 I'm proposing we remove it from the platform. This will
leave HttpBasicAuthenticationModule and HttpDigestAuthenticationModule.
this post up for discussion.
during F2F we have been discussing deprecation of WebSQL DataManager in
because its "rival", IndexedDB, is already supported in all browsers
I suggest we make IndexedDB adapter Stable and supported and Deprecate
Actually both are Experimental in 1.5.2, so there is no reason for
We can also leave it around as long as it does not diverge from other
What are your feelings?
I was thinking about adopting Karma runner for running QUnit tests in
Currently we use grunt-contrib-qunit,
but this runner is able to run tests just on PhantomJS and PhantomJS itself
has some defficiencies, such as it does not support IndexedDB.
Karma, on the other hand, is able to run in all mainstream browsers ,
headless browsers such as PhantomJS, and it has even support for
cloud-driven browsers such as BrowserStack or SauceLabs (through those we
could actually test inside mobile browsers; at least SauceLabs offers free
hours for open source projects).
This would give us pretty good coverage in terms of compatibility testing.
What do you think?
We have staged AeroGear SimplePush Server 0.12.0:
The following JIRAs are included in this staged release:
The tag for this staged release can be found here:
If you have time, please take it for a spin and report back any issues.
Example of testing the Netty server from the command line:
1. Start the server
cd server-netty && mvn exec:java
2. Register a channel
Open a new terminal window:
Send the hello message and then register a channel by specifying a value
for channelID property.
Copy the returned pushEndpoint value.
3. Send a notification
>From your terminal window, use curl to send a notification:
curl -3 -i --header "Content-Type:application/x-www-form-urlencoded" -X PUT
As the subject implies, we will be moving the 2.0 branch of AeroGear.js to master very shortly.
So all current development in the master branch will be for 2.0 and BEYOND!!!11!!!one!11!
There is 1.x branch that will be maintained for bug fixes and such.
Some highlights that will be coming in the 2.x series:
* Removal of Pipeline and Authentication
* Promisfying the Whole Library( where it makes sense )
* ES6 Modules
* Data Sync/Conflict Resolution
* and more….
on yesterday's Aerogear.js meeting we have discussed in which version we
should include Data Sync module. Since we are starting works on ES6
compatibility, which is one of the big features for 2.0, it make sense to
continue with Data Sync there.
What about Android and iOS SDKs? Do you plan to include new module in 2.0
or start that in 1.x and later backport to 2.0?