This change deserves a more thorough explanation. All currently
released versions of Django are based around the concept of receiving a
request and immediately dispatching a response.
WebSocket connections don't follow this convention, and the `request` hangs
around for long periods of time. As such, things like `request.user` don't
really make sense as a user may login, then logout, then login again all
within the life of a single request.
Given that the concepts applied in Django are based upon a premise that
doesn't hold true for WebSockets (that a request is short-lived), it
doesn't make sense to apply those concepts in django-ddp.
session in the database yet, also allow subscriptions from
unauthenticated sessions (but don\'t show any data for collections that
have user_rel items defined).
