June 2013 - aerogear-dev - Jboss List Archives

AeroGear Android & JS API remove operation

by Apostolos Emmanouilidis

Hi guys, While writing some tests for the AeroGear JS API, I came across the following issue: The Pipe.remove method of the AeroGear Android API does not require any data as a response. The callback has Void data. This means that the corresponding operation on the server/backend side returns an empty response. However the AeroGear JS API relies on jQuery AJAX mechanism. When using the Pipe.remove method, jQuery tries to parse the empty response as JSON and it fails. I had to hack jQuery and add the following piece of code in order to use the same backend service for both AeroGear APIs: parseJSON: function( data ) { if (!data) { return null; } If you know any way to make the AeroGear JS Pipe.remove method to work when the server side returns an empty response and without hacking the JQuery, please share it. Thanks, Tolis

12 years, 10 months

2
2
0 / 0

AeroGear LDAP connection

by Yavuz Selim YILMAZ

Hi all, My AeroGear controller needs to connect to an existing LDAP instance. What's the AeroGear recommended approach for this? Currently I heard from Bruno: "If you want to make use of LDAP, you have to stick with PicketLink (http://picketlink.org/) or Apache Shiro (http://shiro.apache.org/). Currently I'm working to make this integration simple. I'd love to hear your feedback and what's missing for you. Open JIRAs to me as needed https://issues.jboss.org/browse/AGSEC" Your comments, thoughts and recommendations are most welcome. Best wishes, --- Yavuz Selim Yilmaz SUNY at Buffalo Computer Science and Engineering PhD Candidate

12 years, 10 months

2
1
0 / 0

Preflight request and AeroGear

by Bruno Oliveira

Morning peeps, on the latest week Kris opened an issue on PicketLink https://issues.jboss.org/browse/PLINK-157 Considered a blocker (https://issues.jboss.org/browse/AEROGEAR-1243). It was fixed few days ago, but PicketLink beta4 wasn't released yet. For this reason I built PL from the main repo https://github.com/picketlink/picketlink and deployed our demo with the latest changes https://controller-abstractj.rhcloud.com/aerogear-controller-demo/ Only for testing purposes, run: - Must return HTTP 200 curl -v -X OPTIONS http://controller-abstractj.rhcloud.com/aerogear-controller-demo/autobots - Must return HTTP 401 curl -v -X GET http://controller-abstractj.rhcloud.com/aerogear-controller-demo/autobots Let me know if you have more questions. - @abstractj

12 years, 10 months

3
3
0 / 0

[off-topic] - Stalking people on GitHub

by Bruno Oliveira

Hi peeps, I just found this project interesting and helpful to manage issues/PRs on github https://github.com/eduardolundgren/node-gh To check all the opened issues/PRs on AeroGear. After the installation just run: gh is --list --all --user aerogear gh pr --list --all --user aerogear Or include it into a shell script - @abstractj

12 years, 10 months

2
1
0 / 0

Authenticator

by marcelo

Hi people, i'm working on an app using AeroGear and having a problem with the authentication. When trying to login to an API http://host/api using authenticator, on the Xcode console I see that it's trying to authenticate against http://host/api/auth/login. How can specify that my login endpoint is host/api and not host/api/auth/login. I'm using the PrestaShop webservice. Thanks in advance. -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Authenticator-tp2982.html Sent from the aerogear-dev mailing list archive at Nabble.com.

12 years, 10 months

3
2
0 / 0

Re: [aerogear-dev] Firefox OS App Day

by Kris Borchers

Great to hear that you guys are interested in collaborating a bit with us! We are really excited about what we have so far and where we want to go with this to hopefully help bring SimplePush to the browser. I have added our developer mailing list to the CC. Another repo we wouldn't mind you taking a peek at is the client side polyfill stuff I have been working on here https://github.com/aerogear/aerogear-js/blob/Notifier/src/simple-push/aer... and the bit that does most of the work is here https://github.com/aerogear/aerogear-js/blob/Notifier/src/notifier/adapte.... It currently lives on a branch for the new Notifier bits I am adding to AeroGear.js for some API unification for different messaging protocols. Basically what we are doing is using websockets (or a fallback) via SockJS and storing some channel info in localStorage for re-registration, etc. Any and all feedback would be appreciated. Even if it's "You're crazy! Don't do that! Do this!" :) Thanks and also excited to be able to work with you on this as well! On Jun 4, 2013, at 10:30 AM, JR Conlin <jrconlin(a)mozilla.com> wrote: > We have push-notifications(a)mozilla.org, however that list is not widely used. I wouldn't mind adding it as a CC to the discussion, however. > > I'm fine using your public mail list, if you don't mind me pointing to it from our wiki pages or summarizing discussion points there. > > Neat, you're implementing a netty version. I'll have to dig into it and see how you're building that out. > > I should also probably mention that to get things up to large scale, the go version I built does a few things different than the strict spec says. <https://github.com/jrconlin/pushgo> > > 1. The server doesn't really care that much about valid channelIDs. > As you know, when you start to have to deal with very large numbers of connections, you really want to reduce your data storage dependencies. Since SimplePush is a "best effort" system (we're not guaranteeing delivery of messages in all cases since that's prohibitively expensive), we merely collect channelIDs for a given UAID and report them to the client on flush. This allows us to not have to do a data fetch, since the client will discard any unknown channelID, passing those values to the client does not cause user facing issues. I can prevent random "griefing" from malicious users by using a simple AES hash on the endpoint. If the hash fails to decrypt, I don't even bother trying to store anything. > > I also don't report back failures to PUT requests. The less information that I give malicious parties, the better, and legit parties will always get the same result. > > 2. I take advantage of memcache's self expiring records to auto-prune entries. Legit notifications live for 3 days. This is based on the idea that notifications tend to be fairly ephemeral and you probably don't really care if an accident slowed down your commute home last Thursday. > > We're excited that you want to contribute and look forward to working with you. > > On 2013/6/4 5:20 AM, Erik Jan de Wit wrote: >> Forgot to add these guys >> >> Cheers, >> Erik Jan >> >> Begin forwarded message: >> >>> *From: *Erik Jan de Wit <erikjan.dewit(a)gmail.com >>> <mailto:erikjan.dewit@gmail.com>> >>> *Subject: **Re: Firefox OS App Day* >>> *Date: *June 4, 2013 8:48:26 AM GMT+02:00 >>> *To: *jr conlin <jrconlin(a)gmail.com <mailto:jrconlin@gmail.com>> >>> *Cc: *Nikhil Marathe <nmarathe(a)mozilla.com >>> <mailto:nmarathe@mozilla.com>>, JR Conlin <jrconlin+moz(a)gmail.com >>> <mailto:jrconlin+moz@gmail.com>> >>> >>> Hi, >>> >>> Great to hear from you, we are building something based on the specs >>> that you wrote. The idea is that this will serve as a polyfill we have >>> a server as well >>> https://github.com/danbev/aerogear-simplepush-server To be able to >>> stay in sync with what you are doing we need have some additional >>> questions is it ok for you to have a discussion on our public mailing >>> list? >>> >>> Cheers, >>> Erik Jan >>> >>> On Jun 2, 2013, at 8:46 PM, jr conlin <jrconlin(a)gmail.com >>> <mailto:jrconlin@gmail.com>> wrote: >>> >>>> Hi Erik Jan, >>>> >>>> Yes, we're the folks you probably want to talk to. Nikhil works on >>>> the Client portion (the elements that run on the device or browser), >>>> and I work on the Server portion. >>>> >>>> We'd love to hear your questions, since we've been fairly deep into >>>> this for a while and it's always good to have folks point out the >>>> confusing bits. >>>> >>>> I can tell you that a bunch of the more confusing elements might go >>>> away if we note that SimplePush isn't supposed to be 100% guaranteed >>>> delivery, but "Best Effort". Doing 100% guaranteed is very expensive >>>> from a hardware and software point of view and costs tend to >>>> seriously escalate once you get past a few hundred users. Instead, >>>> the system tries it's best to send a dataless "ping" to the device, >>>> in many cases, leaving how the ping actually gets to the device as a >>>> responsibility of the system that is closest to the device. >>>> >>>> Think about how email is sent around. Just because you hit "send" >>>> doesn't mean that the email has appeared at the destination. Often >>>> it's handed around to multiple systems before finally making it to >>>> the location. >>>> >>>> In that scenario, "errors" become a bit harder to nail down. There >>>> are definite errors when a device can't talk to it's immediate >>>> server, and we try to handle those appropriately. There are also >>>> potential errors that may happen if an end point tries to ping a >>>> device that doesn't exist. Where things get fuzzy are the errors >>>> around a device that just got run over by a bus or sat in a drawer >>>> with a dead battery for a week. >>>> >>>> In any case, feel free to contact us via email or if you like on >>>> irc.mozilla.org/#push <http://irc.mozilla.org/#push> >>>> >>>> On 6/2/2013 10:10 AM, Henrik 'henx' Mitsch wrote: >>>>> Hi Nikhil and JR, >>>>> >>>>> looking at https://wiki.mozilla.org/WebAPI/SimplePush you seem to be >>>>> the main editors. Last weekend we had a Firefox OS App Day in >>>>> Switzerland. It was awesome! >>>>> >>>>> Erik Jan was one of the participants. He has a question concerning >>>>> Simple Push (see below). Can you guys help him out? >>>>> >>>>> Best regards, >>>>> Henrik >>>>> Mozilla Rep >>>>> >>>>> >>>>> >>>>> On 28.05.13 09:59, Erik Jan de Wit wrote: >>>>>> Hi Henrik, >>>>>> >>>>>> I was talking with my colleges about the nice day we had saturday. >>>>>> And I mentioned that you could bring us in contact with people that >>>>>> build the Simple Push into Mozilla. Like I've explained before we >>>>>> made an implementation as well based off the specs that are on the >>>>>> MDN, but would be nice if we could sync with the one that was >>>>>> developed for Mozilla OS as the specs have some holes. For instance >>>>>> how to handle errors is not really clear. Could you bring us in >>>>>> contact with the people that implemented this in Firefox? >>>>>> >>>>>> Thanks, Erik Jan >>>>>> >>>>> >>>>> >>>>> >>>> >>> >> >

12 years, 10 months

3
2
0 / 0

Hackergarten in Marseille, Aerogear Subjects are Welcome !

by Sebastien Blanc

Hi, I've been invited to a Hackergarten by the MarsJUG (Marseille JUG) in a couple of weeks in Marseille and I have been asked to propose Aerogear subjects to propose. For those, who don't know what a hackergarten is , please take a look at http://hackergarten.net/ , basically : "Hackergarten is a craftmen's workshop, classroom, a laboratory, a social circle, a writing group, a playground, and an artist's studio. Our goal is to create something that others can use; whether it be working software, improved documentation, or better educational materials. Our intent is to end each meeting with a patch or similar contribution submitted to an open and public project. Membership is open to anyone willing to contribution their time." The Hackergarten will last an entire afternoon until (maybe) late in the night ... It's a nice opportunity to give some visibility to the Aerogear Project. But for that I need to propose subjects. We must stay realistic, we can't ask for instance people to write a new Pipe Adapter or implement sync ;). But we can work on smaller tasks, on which we have never the time or that has lower prio : writing extra unit tests / Writing integration tests / Document code ... So If you have ideas, please share them here, All the AG projects are concerned (JS / Android / JEE / iOs) but keep in mind we are dealing with a JUG , so maybe a bit more focus on the JEE and Android projects. Seb

12 years, 10 months

6
11
0 / 0

[SimplePush] Close status codes

by Daniel Bevenius

Simple Push Error codes I'd like to bring up a question that came up while developing the SimplePush Server. The server has a scheduled job that will clean up inactive UserAgents. When it does the clean up, the connection will also be closed by the server (if it is still active) and an error code with a message is returned. This will be a SockJS close frame which looks like this: c[3039,"Connection closed due to inactivity"] Now, the status code which is the first entry above is just something I made up. It might be nice to have a few different error codes to signal to the client the reason for closing, as the client might want to take some action. I've not found anything in the SimplePush Protocol Specification<https://wiki.mozilla.org/WebAPI/SimplePush/Protocol> yet, and thought I bring this up for discussion.

12 years, 10 months

2
2
0 / 0

iOS branch cleanups

by Christos Vasilakis

Hi, just to let you know that today we did a cleanup on iOS projects on github and we deleted unused branches (except 'mantle-AEROGEAR-635' for ios-TODO and 'screenshots' in xcode-template) Thanks Christos

12 years, 10 months

3
2
0 / 0

AeroGear Android Pipe Tests

by Apostolos Emmanouilidis

Hi, We have added some tests [1] for the AeroGear Android Pipes. The tests are executed on TravisCI [2] Both [3] simulation tests (like those included inside the aerogear-android-integration-tests which simulate the HTTP response) and real tests (using a rest service which is deployed on a JBoss AS 7 instance on the TravisCI machine) are executed in each build. The TravisCI build procedure is the following: 1. The Android SDK is installed on the TravisCI headless machine 2. An Android emulator is started (without skin) 3. The REST service is built. Jboss AS 7 distribution is downloaded 4. The JBoss Server is started. This script [4] waits until the server is started up. 5. The REST service WAR is deployed on JBoss AS. 6. The Android tests are executed inside the emulator I'd like to add some cases to test the CORs support. Is there any specific configuration on pipelines/pipes or CORs is enabled and supported by default? [1]: https://github.com/tolis-e/aerogear-android-pipe-tests [2]: https://travis-ci.org/tolis-e/aerogear-android-pipe-tests [3]: https://github.com/tolis-e/aerogear-android-pipe-tests/blob/master/aeroge... [4]: https://github.com/tolis-e/aerogear-android-pipe-tests/blob/master/wait_j... Thanks, Tolis Emmanouilidis

12 years, 10 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

aerogear-dev June 2013