So, in your mind, where should the handle for applying session security go? (Header
Tokens, signing, url params, etc)
----- Original Message -----
From: "Matthias Wessendorf" <matzew(a)apache.org>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Sent: Friday, November 9, 2012 1:47:50 AM
Subject: Re: [aerogear-dev]
[Android] AuthenticationModule.applyAuthentication(HttpProvider)
I have seen that method.
For me, I am not sure I really want to expose something like that to
the endusers... For me the auth module is basically the facility where
users of the library (-> app devs) are doing enrollment, login and
logout
Not really to thrilled about doing that in iOS...
-M
On Fri, Nov 9, 2012 at 4:55 AM, Summers Pittman <supittma(a)redhat.com> wrote:
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?
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev