
Sign up to save your podcasts
Or


Any complex Django-based app will include many models that use the DateTime field, and the clients use those fields.
Assuming all our clients will always be in the same timezone is wrong for a globally used app.
When designing a flow that handles DateTime fields in server-client data exchange, timezone conversions are the main issue.
Another challenge is what can we assume about the DateTime data that comes from the client when they send a PUT request with a DateTime field? What should the response assume? What if the client sends a GET request without any additional data?
In this talk, we will address those issues by demonstrating a simple “Timed Assignment App” that can be used globally.
By Any complex Django-based app will include many models that use the DateTime field, and the clients use those fields.
Assuming all our clients will always be in the same timezone is wrong for a globally used app.
When designing a flow that handles DateTime fields in server-client data exchange, timezone conversions are the main issue.
Another challenge is what can we assume about the DateTime data that comes from the client when they send a PUT request with a DateTime field? What should the response assume? What if the client sends a GET request without any additional data?
In this talk, we will address those issues by demonstrating a simple “Timed Assignment App” that can be used globally.