[Android] Interfaces on Pipeline, Datamanager, and Authenticator
by Summers Pittman
(See https://github.com/aerogear/aerogear-android/pull/33)[Yes it isn't coarsely separated, it is just a bunch of proof of concept stuff]
Right now in ag-android Pipeline and DataManager are final and concrete. Authenticator is an interface implemented by the final class DefaultAuthenticator. I have coded up a proposal where I've (among other things) split the other classes up.
Pros for Interface + final class:
Easier mocking for unit tests (thinking about users' unit tests not ours)
Better practice (is Josh Bloch is to be belived)
Cons:
Pipeline et all are entry point classes and we shouldn't encourage our users to write their own
We can make Pipeline et all non-final to allow users to mock them for their tests.
Thoughts from the list?
13 years
[Android] AuthenticationModule.applyAuthentication(HttpProvider)
by Summers Pittman
I added a method to AuthenticationModule, "applyAuthentication(HttpProvider)". Before the RestAdapter (subclass of Pipe) class had to know details about how the AuthModule / Auth Strategy worked to apply a token. IN this case the handling of security connections is done by the module instead of the Pipe.
Wdyt about adding it to the ios and js libraries?
13 years
AeroGear security updates
by Bruno Oliveira
Morning slackers,
Just to give a heads up to you about AeroGear Security about some changes:
- AeroGear security was splited in two projects: aerogear-security (https://github.com/aerogear/aerogear-security) and aerogear-security-picketbox (https://github.com/aerogear/aerogear-security-picketbox)
- The HTTP status responses we're improved to support RESTful endpoints and AG controller
- A bunch of code refactoring
- The documentation was updated
- The aerogear-controller-demo was updated (https://github.com/aerogear/aerogear-controller-demo)
- OTP authentication as integrated tested and few bugs were reported to the PicketBox team. For now we're not ready to go on it.
- Our API was upgraded to the latest timed release on PicketBox/PicketLink (https://docs.jboss.org/author/display/SECURITY/Timed+Release+2012-Nov-06)
What's missing?
- Release it as snapshot on nexus, currently under maintenance.
- Include the Javadocs
- Code improvements
- Catch up with PicketBox team and figure out why OTP is not being validated
- Improve token validation on ServletFilter (for now is just disgusting)
- Integrated HTTP status responses with AG controller (for now AG security just throws a security exception and returns HTTP status code to RESTful endpoints)
Bugs? Please @jira https://issues.jboss.org/browse/AEROGEAR
--
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
13 years
Details on the build process and dependencies
by Jay Balunas
Hi All,
One thing we need to be sure to document is the details of our build process and dependencies for each of libraries and repos.
The question is whether to centralize these or keep them with each of the respective repos? Thoughts?
If we the repos we should adopt of specific convention for the files and the names. i.e. BUILD.md, and/or DEPENDENCIES.md.
Wdyt?
Thanks,
Jay
13 years
JSON Serialization in Android
by Summers Pittman
Right now we have JSON serialization in Android implemented by a default configuration GSON instance.
I am updating the docs to note this, however it is "only" an implementation detail.
1) Do we want to say for 1.x that GSON IS the library we are using? (Yes)
2) Do we want to provide a configuration point for Serialization (GSON if yes to 1, something more general if No)? (Yes, but not for 1.0)
2.1) How much do we want to expose/allow to be configured? (No idea)
Relevant Jira:https://issues.jboss.org/browse/AEROGEAR-596
Summers
13 years
[aerogear-controller] Default Error Page
by Daniel Bevenius
Hi all,
I wanted to get some input on what you'd like to see on a default error
page in aerogear-controller. This is the page that a user will see if an
error occurs, and no custom error route has been defined.
I'm attaching a screenshot of what I'm playing with at the moment.
Some thoughts:
1. Should we be showing the stacktrace at all?
2. Should we have a button which can be used to display the stacktrace?
Any suggestions are as always most welcome.
Thanks,
/Daniel
13 years
