Re: [aerogear-dev] [Android] - Refactoring OAuth2 configuration
On 03/09/2015 12:15 PM, Erik Jan de Wit wrote:
> 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. Push is an exception ONLY
because there isn't an equvalent open solution which has the same reach to devices.
It’s just some configuration, what point does oauth2 have when it doesn’t work with
Facebook and Google.
/me looks at the shoot and share demo, and the gdrive demo.
Looks like it does work with FB and Google. Did you have a specific
example in mind?
The whole point of our libs is to make it easy for developers to do
these complex things adding this config makes it super easy. I don’t see: ”Terrifyingly
bad karma” a good reason not to do this.
Because it is hitching our open source
project to the largess of
proprietary service vendors. If they change THEIR configuration and OUR
libraries break WE look like the bad guys not them for starters.
Additionally the only direction this can go is toward scope creep. Once
we have Facebook and Google nothing is stopping (rhetorically) from
adding Facebook, Yahoo, VK, Microsoft, etc. Now we are maintaining 5x
as many configurations as we were before. Who is going to monitor those
APIs and make sure they don't break/get deprecated? Do we cut a release
because one auth provider changed their config?
Of course we don't because that is the responsibility of the app
developer to make sure their configuration for the services they consume
is up to date. It is not and should not be our responsibility.
I freely admit it is nice and it is convenient but it does not belong in
the project.
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Summers Pittman
>Phone:404 941 4698
>Java is my crack.