Apologies if this has been asked before but I'm struggling to find any real best practices.
I'm developing a site using Django using the built in user authentication module. This is all working fine and users can register, login, etc. on the web site with no problems. The plan is to also have companion iPhone/Android apps where users can register/login and then access their data on the main site. This is where I'm a bit unsure of how to proceed. I've been looking into using TastyPie to create a REST API which I think will work fine for accessing/updating data but I'm not sure if this is appropriate for creating new users and authenticating existing users. The other alternative would be (I think) to create a login form in the app which posts to my web site log in form and will return the usual session cookie. The registration form could do something similar again directly posting to the view rather than accessing the API. Does anyone have any opinions as to which of these options are best? I kind of feel using an API would be consistent with how the rest of the app will work but the lack of any examples of this on the internet leaves me wondering if this is a bad idea. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/mlu3FyMtvf4J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
