On Fri, Nov 30, 2001 at 05:02:35PM +0100, Stefano Mazzocchi wrote: > Jeff Turner wrote: [..] > > I > > understand the reason for this; the only problem is that when Cocoon 3 > > arrives, everyone's URLs will break again. A nicer solution would be to > > have: > > > > http://xml.apache.org/cocoon1 > > http://xml.apache.org/cocoon2 > > http://xml.apache.org/cocoon3 > > > > and then use mod_rewrite to make http://xml.apache.org/cocoon/ reflect > > whatever is the current version. > > Forget it! The Cocoon homepage *is* http://xml.apache.org/cocoon/. > > Period. > > We will never have other URIs, we'll keep all the documentation inside > and work more evolutionarely from now on (no big transitions).
What use is a stable URI if the resource it references keeps changing? Say I write a HTML page, "How to install Cocoon 2 with FooBar extensions". I want to reference the content currently at: http://xml.apache.org/cocoon/installing/ But I can't, because when Cocoon 2.x or 3 comes out, it won't be the same content I intended to reference. It's a Cool URI, but it ain't a Cool Resource, because it keeps changing :) My mod_rewrite suggestion above is one solution; have two URIs per resource, one stable, one changing. This is far from a Cocoon-specific problem though. It would be nice if there were a HTTP header, by which one could specify "Give me the version of resource X at date Y". This could even be implemented with Cocoon, if there were a magic "date" param, and if there were a "cvs://" protocol to provide a backend. Hmm... --Jeff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
