[aerogear-dev] Authentication endpoints

Thu Oct 4 14:20:50 EDT 2012

+1 to enroll method name

let's keep the endpoints

-Matthias

On Thu, Oct 4, 2012 at 8:17 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
>
> +1 to enroll method name
>
> On Oct 4, 2012, at 2:14 PM, Kris Borchers <kris at redhat.com> wrote:
>
> OK, how about this … we change the method name to enroll and can either
> leave the endpoint as register or change to enroll as well if we want. That
> will fix the iOS issue and still make sense.
>
> Any thoughts?
>
> On Oct 4, 2012, at 12:59 PM, Kris Borchers <kris at redhat.com> wrote:
>
> I don't understan why we're still considering changing the name of the
> endpoint since it has no bearing on the method name.
>
> On Oct 4, 2012, at 12:51 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> Let's just rename 'register' to 'registration'. I'd like to rename to
> AUTH/BOOOOOOOOM, but people could complain.
>
>
> --
> "The measure of a man is what he does with power" - Plato
> -
> @abstractj
> -
> Volenti Nihil Difficile
>
> On Thursday, October 4, 2012 at 10:22 AM, Kris Borchers wrote:
>
> I would vote no since IMO login and logout are more common. I would be ok
> with renaming register to signup I guess, but don't see the need.
>
> On Oct 4, 2012, at 8:20 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>
> I guess the question is still, do we want to rename the default endpoint
> names ?
> /auth/signup
> /auth/signin
> /auth/signout
>
>
> I guess that's why Bruno sent the email (regardless if the API has
> hooks to override or not)
>
> -M
>
> On Thu, Oct 4, 2012 at 2:56 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
>
>
> On Oct 4, 2012, at 8:54 AM, Kris Borchers <kris at redhat.com> wrote:
>
>
> On Oct 4, 2012, at 7:51 AM, Lucas Holmquist <lholmqui at redhat.com> wrote:
>
> even though the URL doesn't matter, we should probably keep the function and
> endpoint the same, just for consistency and simplicity for the application
> dev.
>
>
> I don't agree. In JS, the endpoint is completely configurable so it doesn't
> matter. The user could have the method register() point at
> /LOOOOOOOOOOOL/BOOM if they wanted to so I don't think the method names need
> to match the endpoints.
>
>
> Thats true, brain fart
>
>
> and they should be consistent across the lib's so if someone who used
> aerogear.js decides to become an iOS programmer and uses Aerogear.dmg(or
> whatever it's called), then they already know the api
>
>
> I do agree however that what ever we decide, we should try to be consistent
> in our method naming across libs.
>
>
> -luke
>
>
> On Oct 4, 2012, at 8:25 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>
> On Thu, Oct 4, 2012 at 2:21 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> Morning guys, I was talking with Matthias this morning about our
> authentication endpoints, he brought up a important concern.
>
> Currently we have:
>
> /auth/register, /auth/login, /auth/logout. The problem here is about
> 'register', a reserved word in some programming languages like Objective C.
>
>
> the endpoint URLs are not an issue (just a URL).
>
> But I can't name an iOS/ObjC function 'register'
>
> -M
>
>
>
> Alternatives:
>
> - Change 'register', to 'registration'
> - Change the endpoints to signin, signout, signup.
>
>
> Wdyt? Suggestions?
>
>
> --
> "The measure of a man is what he does with power" - Plato
> -
> @abstractj
> -
> Volenti Nihil Difficile
>
> _______________________________________________
> aerogear-dev mailing list
> 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
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> 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
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> 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