ZebZiggle wrote: >I'm sure there are many very large websites using Django, but from what >I see many are newspaper-style (many reads, few if any writes except by >the admins). I'd be curious how may sites are doing dynamic updates by >many concurrent users? > It's still not a problem for a typical web app (think of eshops) that indeed does many concurrent updates. The thing is that these updates are targeted at different data: each user updates its own piece. So another condition that should be applied to your problem description is that there should be many concurrent updates to shared data.
And even with such updates the problem would exist only with applications that keep modified data in memory for later access. Again it's not the case for a typical web app where each request does a short cycle of read-process-update. Most of the time most of the state is stored in a database and not distributed across many concurrent processes. I do agree that the problem exist. However I don't agree that it's common enough to cliam that Django can only support single user scenario :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
