We're using django as a front end to a pre-existing web site implemented in PHP. The PHP code has a vaguely RESTful interface, where you can make HTTP calls on it and get back JSON-ized data. The django layer sits in front of that and talks directly to the browser. We're not using any models in django; just using the views to render django templates using the data from the PHP back end.
Authentication on the original site was via session cookies maintained in the browser. We're trying to figure out how to make the django layer deal with authentication. My thought is that it shouldn't. It should be entirely stateless, and just transparently pass cookie headers back and forth between the browser and the PHP back end. Probably by using some middleware to do this. Has anybody done anything like this before? Am I heading off into weeds? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
