Closed ProLoser closed 11 years ago
Hi, you are free to fork and push this to AngularUI. I have nothing against that idea, I am, however, not sure if that is good for AngularUI.
The problem with authentication is that there are so many ways to do it, every one can implement theirs own mechanism for that.
Again, feel free to use my work, I would be happy if people used and liked it.
My thought is that it needs to be reworked, although your implementation seems to be good enough and lite for most solutions. There are plenty of 'not necessarily the best solution' in AngularUI, we simply provide them for the 80% of those who could use them.
On Tue, Aug 21, 2012 at 2:05 PM, Witold Szczerba notifications@github.comwrote:
Hi, you are free to fork and push this to AngularUI. I have nothing against that idea, I am, however, not sure if that is good for AngularUI.
The problem with authentication is that there are so many ways to do it, every one can implement theirs own mechanism for that.
Again, feel free to use my work, I would be happy if people use and like it.
— Reply to this email directly or view it on GitHubhttps://github.com/witoldsz/angular-http-auth/issues/1#issuecomment-7916186.
Dean J Sofer DeanSofer@gmail.com
BS Computer Information Systems California State Polytechnic University, Pomona Telephone: 714-900-2254 Website: www.DeanSofer.com Github: github.com/ProLoser
We get this question a lot and the implementation you have here seems pretty simple/straightforwards. We're always looking for more team members and you'd get a lot more support for further development.