On Android and iOS you CAN mix data keys in the datastore, but this will
cause the readAll method to fail.
On Android we are planning on fixing this (there is a JIRA somewhere) to
make it so that we will do simple key checks.
begin mixing/matching keys.
I was having some thoughts on the future of AeroGear.js that i needed to share.
I think i want to create a branch that is very experimental, that targets new and upcoming API's, like Object.Observe, and Promises, etc…
I feel this is the only way to drive innovation
I was thinking this is sort of our "Canary" branch, and when things start to become less pollyfilly, then we can start to move these features in.
I still however want the code in this branch to be complete, not just random crap
I would like to see that in 2.0 we start to remove our jQuery requirement, and focus more on Modern Browsers and have our 1.X branch be our less than modern browser( IE9 ) supported branch. much like how jQuery has a 1.X and 2.X branch, obviously the difference between our branches won't be as extreme.
The major thing we use jQuery for atm is jQuery.ajax and Promises. this is nice for cross broswer compatibility and for transpoting other things other than json, which brings me to my next point
I would also like in 2.0 to make our library( pipeline ) only speak json. I think this will make it really simple to have our own AeroGear.Ajax() method and be able to keep it small in size
Once we hit all our 1.X milestones( sync, offline ) then what is the current master branch would become a 1.X branch, and we recieve bug fixes, but no new features. If something in the future could be back ported, then maybe, but it wouldn't be a priority
This branch would still have a jQuery requirement and would be for legacy stuff( IE9 )
So in JS land and iOS land we have or will soon have OAuth2 handling.
To handle OAuth2 a new API was created, AGAuthorizationModule. I
understand and agree with the separation of concerns between
Authentication and Authorization, but I am worried that this introduces
two APIs now.
Before Authz was added Authentication (login, logout, etc) and
Authorization(here are my keys and permissions) were both handled by
AGAuthenticationModules. With Authz now being a thing we should
probably remove and deprecate the authz parts of the old
One of the things I brought up in the review of the iOS OAUTH2 PR was
that the Authz factory class, AGAuthorizer, does not allow injection of
Corrine mentioned that this wasn't done for any of the other classes
(Pipeline, Authentication, etc). I know Android does this (via an add
method and also allows you to supply a custom builder) and I am pretty
Just wanted to bring up this place where the platforms diverged and get
Back to coffee,
On Jan 20, 2014, at 12:04 PM, naveenraj bala <mailnaveenraj(a)gmail.com> wrote:
> I would be glad if i also knew about both . You made me courious. Do you have road map for FireFox OS . I never saw any like that.
as for Firefox Mobile on Android, we are in the process of revamping our supported browser targets, but there is no reason that it, aerogear.js, shouldn't work fine since we currently use jQuery behind the scenes to do ajax
> Naveen Raj Balasubramaniam
> On Mon, Jan 20, 2014 at 7:25 PM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
> Hi, are you talking about FireFox OS or the firefox Mobile Browser on Android?
> On Jan 19, 2014, at 4:06 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
>> Hello Naveenraj,
>> Besides the mentioned app, last week Erik Jan also did create an new app, for FirefoxOS:
>> It is basically a port of our 'push show case'.
>> I think these two different apps should give you a good starting point, how to use AeroGear APIs on a FirefoxOS device
>> On Sun, Jan 19, 2014 at 9:49 AM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
>> Good morning my friend, not yet. But if you want to start with something, Daniel Passos wrote an application using AeroGear JS (https://github.com/danielpassos/call4paperz4FirefoxOS)
>> On January 18, 2014 at 5:22:42 PM, Naveenraj (mailnaveenraj(a)gmail.com) wrote:
>> > > I just wantbto know if mozilla Firefox mobile is supported or
>> > not.
>> > In the tbd of mobile browser I am not able to find Firefox mobile.
>> > .
>> aerogear-dev mailing list
>> Matthias Wessendorf
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> aerogear-dev mailing list
We've been making a lot of progress on sync, but as many of you likely already know it is not ready for a full focused release. Much like encryption, sync is a significant feature and is still in active R&D and likely needs multiple iterations given its complexity. Its much better to let this mature organically that force it out the door before its out of diapers :-)
So with that said, I propose postponing the planned January umbrella release. I think we should revisit our roadmaps and plans during this time, before trying to set new release dates. While we do this we should make sure to add in time for updates to docs, examples, getting started items, site, cookbooks, etc...