tag:blogger.com,1999:blog-10939740.post8176110835695341141..comments2008-06-04T11:50:36.501ZDan Taylorhttp://www.blogger.com/profile/14353661015592665890noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-10939740.post-6110636957953208902008-06-03T22:04:00.000Z2008-06-03T22:04:00.000ZSean McGrath discussed this issue at last months's XTech Conference. He identified three models currently operating on the web:<BR/><BR/>1. Pages on the server that are then statically published.<BR/><BR/>2. documents existing on the server but dynamically rendered transforming the content in the process using, for example, CSS and JavaScript.<BR/><BR/>3. nothing existing until you observe it. The document is composed and rendered when requested on the client - Just In Time programmatic generation of content.<BR/><BR/>I think we have a 4th class - like /programmes - where pages are rendered JIT on the server.<BR/><BR/>But in any case it is model 3 that's causing the problems you rightly highlight. At the most extreme the pages really can't be thought of a being part of the web - they can't be indexed by Google bots, bookmarked or linked to. <BR/><BR/>And that's before, as you point out, you get to reusing urls. Sigh.Derivadowhttp://derivadow.com/noreply@blogger.comtag:blogger.com,1999:blog-10939740.post-60699071460353142742008-06-03T00:20:00.000Z2008-06-03T00:20:00.000ZDan - Thanks for the good words about iterasi! The advent of dynamic content creates an entirely different universe. It's cool to to think it's a part of the web we are just starting to explore.Alex Williamshttp://iterasi.blogspot.comnoreply@blogger.com