Mike Malone wrote: > At Pownce, for example, we stick users to the master database for some > period of time (a couple of seconds, usually) after they post a new > note.
Another approach that I took in mysql_replicated[1] is to serve a page that user GETs from a redirect after successful POST always from the master. It certainly doesn't solve the problem in general but it's good enough (for us at least). But I'll second that this damn lagging thing is pretty hard to solve in a general way. [1]: http://softwaremaniacs.org/soft/mysql_replicated/en/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
