I think this could be an awesome scale up feature for larger sites. Proides a roadmap for developers if the hit it big with an app and reduces the re-write time down the track. Although database design is till crucial to larger scaling apps. (ie archiving, partitioning, specific user domain tables etc) I am wondering if it can be implemented to also suit GAE as GAE have huge resources that can be tapped.(they do have a ceiling at the moment as it is still in beta but you can't go wrong having google as your backer) To compete with Rails (as rails as a reputation of not scaling to well) I think we should have this implemented. My two cents worth anyway.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
