python - Sending data to django site -


I am trying to create a Django service for which many client data will be sent. Each customer will represent the authenticated user, whether or not to connect to the Internet, so the customer will collect data and send them when the connection is available. Data should be retained at the local level so that the server can be delivered quickly without hitting it.

The nature of the data is simple, it has to do with game achievements, so each user will have a collection of their accomplishments. As a result, there are no stability issues, because each user is sending their achievement statistics, and no user will edit any other's data.

I am trying to find the most suitable medium for this. My first idea was POST HTTP request, which will handle the DNS server. A Python client will log in and execute these requests and send 'Data' data. Can someone recommend a better option or tell me the reason why this setup is suitable or not?

I would also like to know what you would suggest about the format / method for obtaining data from the customer side. I was thinking json or yaml

Edit 2: This question has been revamped after the recommendation of S. Lot.

Many people like this for this.

We have our own (Pustan Swan has not been published yet) Yes, you can handle a tragedy post request in Dejango with a JSON payload. Although ... Normally, handling is a pain in the neck because transmitting a visual function based on the method (GET, Post, Put or Delete) is not part of the degeneration. You can roll your own method-based dispatcher, but - in the long run - you will be unhappy with the roll-own solution

The piston is not "extra overhead" Are you describing Not - in fact - the simple piston has the right amount of overhead for it.


"A customer who collects these calls in a local database and then synchronizes them with the server." Very Complexity

If these incidents occur at an indefinitely large rate (100 seconds per second), then you will need a multi-process Apache front-end which will allow many DJGEnga back-end to mod_wsgi runs through.

But the clients synchronizing for a central database will be very complex. There are lots of open questions about customers, due to some data and crashing or being infected twice because someone did not apply it twice, when it should not have happened. Avoid too many problems with "database synchronization".


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -