Fix create in newer Tastypie and jQuery (kipped retro-compatibility)

[gartz]

Fixes the CREATE method when django-tastypie response only using the page status without a body content;
Make it compatible with old backbone version (0.9.x or older)
Add package.json to be able to use npm install for this package

[PaulUithol]

What does this fix, exactly? Can you show that, possibly though a test case?

[gartz]

The old backbone doesn't have the ajax property, that bind's JQuery or other lib ajax method, so it need to check if Backbone.ajax is present, if isn't it need to try other required lib ajax, like JQuery.

The other change is about xhr response, when you are creating something, tastypie only returns an empty file with the status code, so the resp is empty, but the action has been succeed, creating the item. So when it test and get no response, it thinks it fail, but the request status is success, then we have problems with creating itens, they where created, but in the clientside it still thinking it wasn't created and keep using CREATE instead UPDATE. This fix make only depends from STATUS code and get the right URI to ensure client model represents the created on the server-side.

After this changes it worked on our Django with Tastypie.

I can't create the test case right now, but if you want to test, the first case you simply remove the "ajax" property from Backbone and run the code (backbone 9.x and before doesn't have that property) and for the second, just send a response with only status and none json, resp will become undefined or empty and the !resp will make it believes that isn't been created even when it has been created.

[helber]

I think this is useful to me.

[gartz]

I have added the package.json to we can use npm install in this package.