We are currently working on a project that loads and dumps very big JSON objects. We recently had some slowness issues and though giving a try to some C compiled JSON modules could give a boost to our API.
After some googling we found out a few exsting modules and decided to setup a benchmark to decide which one to use. The selected modules are:
Let's imagine you have a view somewhere on your website you want to password protect using your usual django login but you are too lazy to design a form to input your credentials. This makes sense if the view is for your own use and you don't need to have a fancy login page. In such a case the easiest and fastest way to proceed is to use the standard HTTP basic authentification to let your browser asks for your credentials.
It is then easy to get the user / password back in your view and to authenticate yourself into django. Here is the code snippet to do this :
fromdjango.httpimportHttpResponsefromdjango.contrib.authimportauthenticateimportbase64defmy_view(request):if'HTTP_AUTHORIZATION'inrequest.META:auth=request.META['HTTP_AUTHORIZATION'].split()iflen(auth)==2:ifauth.lower()=="basic":username,password=base64.b64decode(auth).split(':',1)user=authenticate(username=username,password=password)ifuserisnotNoneanduser.is_staff:# handle your view herereturnrender_to_response('my_template.html')# otherwise ask for authentificationresponse=HttpResponse("")response.status_code=401response['WWW-Authenticate']='Basic realm="restricted area"'returnresponse
If you need to protect more than one view you should wrap this code in a view decorator.
Please not that using HTTP basic authentification your username and password are sent base64 encoded but as it can be easily decoded you should have your website served over https to keep your crendentials secured.
If your application has a model with a ForeignKey on an other model which gets a lot of entries in the database, the auto-generated admin interface can become a nightmare to load. Django will render your ForeignKey using a select drop-down and with thousands of entries loading time and browser memory are in bad shape.
Solution is rather simple, add your ForeignKey in the raw_id_fields parameter in the Django admin. Lets consider this example :