[aerogear-dev] [Android] - Refactoring OAuth2 configuration
Summers Pittman
supittma at redhat.com
Mon Mar 9 12:40:38 EDT 2015
On 03/09/2015 12:18 PM, Matthias Wessendorf wrote:
>
>
> On Mon, Mar 9, 2015 at 4:11 PM, Summers Pittman <supittma at redhat.com
> <mailto:supittma at redhat.com>> wrote:
>
> On 03/09/2015 11:06 AM, Erik Jan de Wit wrote:
>>>>
>>>> Thoughts? Let me know if the idea is useless.
>>> The thought of supporting vendor specific configuration details
>>> makes me
>>> cringe.
>>
>>
>> It convenient and not likely to change
> Because Facebook and Google are well known for not making
> arbitrary changes to public apis and configurations.
>
> More importantly as an Open Source project hitching our code to
> the configuration of a third party proprietary system is
> terrifyingly bad karma.
>
> I disagree. We offer free OS code for these services, and users are
> likely using them, therefore it's nice to have these explicit config
Yes it is nice to have.
>
> Push is an exception ONLY because there isn't an equvalent open
> solution which has the same reach to devices.
>
>
> I don't think that push is an exception due the lack of an OSS
> service, which the same range. Even in the case there was something
> like that, we'd still have same config for GCM/APNs, for a good reason
You are conflating the two arguments. If Push had a simple standard
configuration that didn't require propriety APIs and code then I would
make the same argument. Test their providers for compatibility, show
examples using those providers, and document how to do it. We would NOT
hard code their proprietary configuration into our libraries.
As it stands there is NO standard for Push that is available to 99% of
devices in the same way OAuth2 over HTTP is. The open source solutions
do not have the breadth that we need RIGHT NOW. So we link against and
include explicit in code support for proprietary services. Each Push
implementation is its own bespoke implementation that we hide behind
PushRegistrar interfaces.
>
>
>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <mailto:aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150309/7e9e8ff0/attachment-0001.html
More information about the aerogear-dev
mailing list