One thing no one has mentioned so far is that there will be no support for a relational database. I personally think this is a good thing so people can realize that other datastore options are available. In many cases these alternative options often provide a superior solution for a particular project over a solution built around a relational database.
I personally don't feel that working out rule dispatch, Genshi, or removing C extension issues are going to be the biggest hurdle. First C extensions are not really going to matter much when your code can potentially run on 100 if not 1000s of nodes. At least this is more of an issue for Google to worry about is they want to reduce the computation loads or huge sites that may incur a significant cost due to CPU time. But whether or not you use the c extensions or not you code will likely be severed faster on the Google servers as the processing load due to any request will not affect the speed at which other request are served. Also, I'm sure the request from there datastore will likely be upwards of 100+x faster than a relational database which will help offset the additional latency introduced by using pure python modules over c extensions. The rules dispatch code for error handling could be replace by a naive pure python implementation which would severely reduce the number of request/sec a single web server could handle but for running on 100s to 1000s of node this shouldn't be much of an issue. A more optimized and complex solution could be developed in the future. I don't know of the issues with Genshi but I suspect they are also related to optimizations. The real issue I see is building up the RAD tools around a new datastore will require the largest amount of work. As well as convincing others that it's ok to use a datastore other than a relational databases. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
