Nico-- This is a long, well-thought out post. I haven't had time to digest everything. But I do want to respond to this particular item:
> Having said that, I do support the need for being able to do some > server-side rendering, but almost exclusively because of Google and > indexability purposes, and to a lesser extent for creating initial views > on slower devices. However, having to redo a significant chunk of our > templates to support this seems like a waste of time at this point. > Therefore, similar to Eli's suggestion, I've been working on a > proof-of-concept that uses Node.js to render the initial widget view > either server or client side. In the PoC, Node.js detects whether or not > it's a search engine spider, and if so, renders the initial view > server-side. We need to be careful here. Detecting search spiders and serving them different content is called cloaking, and it's against Google's terms of service. It can get you blacklisted out of search results. See [1] for the official Google policy. Re-using the existing templates sounds like a good idea. Why not cache the initial page views on the server side once Node.js has rendered them? Then we could serve the cached copy to everybody, spider and human alike. [1] http://support.google.com/webmasters/bin/answer.py?hl=en&answer=66355 -chris _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
