Thanks for the kind words. I have the dyndns stuff implemented for myself but didn't include in the image. I'm still working all that out.
Here's a good post with some great ideas on scalability: http://developer.amazonwebservices.com/connect/thread.jspa?messageID=57395 It looks like he is having instances post host information to S3 where all the servers are going to for updates on who is in the cloud. My guess is something like that would work well. I will be experimenting with an implementation similar to that at some point as I will eventually need that level of scalability. I will probably contact Steve for some insight. I'm also working out the writing WAL to S3 every 2 or 3 minutes. Have you got that implemented yet? Michael On 6/2/07, Frédéric Sidler <[EMAIL PROTECTED]> wrote: > very nice job and thanks too for sharing > > I have a instance running django stuff on EC2 too with dyndns.org set up. > Everything is on one instance and I plan to multi-tier this application. > > As we are experimenting teh same solutions, do you have anything to share > regarding this special stuff on EC2 > (http://media.djangobook.com/content/chapter21/scaling-5.png > ) and the fact that an instance is not persistent and this product could > fill the gap (http://www.openfount.com/) --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
