Ok, I start to understand now. To be frank the docs are a bit alarming :)
Le mercredi 25 janvier 2017 08:47:06 UTC+1, Andrew Godwin a écrit : > > >>> I am not sure to understand. In which case can there be messages/frames >> lost?! Where does that happen? Between the server interface and the Django >> layer? I would need to know more about that... Otherwise I might need to >> move with uWSGI or something.... JSON-RPC in itself doesn't implement a >> timeout, althought the javascript client better have one... >> >> > It simply means that it's possible that you might lose an incoming frame. > This is also true of implementing it in uWSGI (the process handling the > socket might get OOM killed, or the server might die, etc.) > > It's not a normal case, it's just that if something super bad happens, the > resulting handling is to drop a message rather than play it twice. Most > systems I know of that handle websockets do this. > > Andrew > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/97e75375-6caf-4e8d-a781-be6da421840d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
