News for hackers. Stuff that matters.
Re:Backbone.js and Django by paulsmith on Tuesday July 05, 2011 @07:25PM (#2731994)
Instead of creating a cookie manually, you can save 4 lines and use the .set_cookie()[1] method on the response object.

Also, take a look at the render()[2] shortcut function to collapse the template loading, context settings, and rendering steps into one.

[1]: https://docs.djangoproject.com/en/1.3/ref/request-response/#... [2]: https://docs.djangoproject.com/en/1.3/topics/http/shortcuts/...

Re:Backbone.js and Django by chernevik on Tuesday July 05, 2011 @09:15PM (#2732206)
Further line saving: The << methods >> dictionary isn't needed, it's just mapping lower case strings to upper. Replace:

return methods[request.method](request, item_id)

with:

return request.method.lower(request, item_id)

Re:Backbone.js and Django by theroo on Tuesday July 05, 2011 @07:45PM (#2732030)
Also, setting the cookie 'todos' to todolist.id will allow anyone to manipulate the value of that cookie in order to read anyone's cookies.
Re:Backbone.js and Django by po on Wednesday July 06, 2011 @12:51AM (#2732612)
With Django 1.4 (or the dev version) it will be possible to cryptographically sign a cookie:

https://docs.djangoproject.com/en/dev/topics/signing/

You can use this to store the session data with the user without having to consult a database and without fear that they will tamper with the id:

https://github.com/ericflo/django-cookie-sessions