I think you're mixing up the concepts of files and resources. persistent URLs should AFAIR bind to resources, which in turn may represent a file (and may redirect to a URL for that file, or something like that).
example (contrived): http://cocoon.apache.org/manuals/BeginnersGuide this, being a resource may be permanent. the actual representation/file delivered (redirected to) may be html, pdf, whatever. and it may well be a different version of the document (e.g. this resource always redirects to the most recent version). that depends on how specific the contract is. you could also have http://cocoon.apache.org/manuals/BeginnersGuide/1.0 which should represent the resource with the specific version. and finally you could specify http://cocoon.apache.org/manuals/BeginnersGuide/1.0/html or something alike. so I think the minimum contract of your file URLs is that a file exists at that url. to your last question: if i saw an url like http://cocoon.apache.org/manuals/beginner_1.0.html I would expect it's always going to be the same file. > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]Im > Auftrag von I-Lin Kuo > Gesendet: Mittwoch, 29. Januar 2003 19:20 > An: [EMAIL PROTECTED] > Betreff: RE: Cocoon for persistent URLs > > > That's what I was thinking, more or less. I'd have a monitoring > application > check URLs once a day and generate emails if the files were moved or > modified. But I was wondering if there were other approaches... > > There's also the contract issue of what a persistentURL promises: does it > merely promise that there will always be some file at that URL, > or does it > promise it's always going to be the same file at that URL? > > I-Lin Kuo, Ann Arbor, MI > Macromedia Certified ColdFusion 5.0 Advanced Developer > Sun Certified Java 2 Programmer > Ann Arbor Java Users Group (www.aajug.org) > > ----Original Message Follows---- > From: "Geoff Howard" <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: <[EMAIL PROTECTED]> > Subject: RE: Cocoon for persistent URLs > Date: Wed, 29 Jan 2003 12:22:06 -0500 > > don't know how one would keep track of moved files automatically, but the > resource exists action could help with the first part. you could keep a > lookup table in database or xml with old location and new location and use > it to lookup new location when resource exists action fails. > > Geoff > > > -----Original Message----- > > From: I-Lin Kuo [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, January 29, 2003 10:57 AM > > To: [EMAIL PROTECTED] > > Subject: Cocoon for persistent URLs > > > > > > Has anybody here used Cocoon to implement persistent URLs? I > > don't mean just > > technical using Cocoon to make the URL independent of the actual file > > location (that's simple using sitemaps), but am interested in how > > to manage > > this. For example, some of the issues are: > > - making sure the file exists at the remapped URL and what > to do if it > > disappears or is modified > > - how to keep track of files that get moved. > > > _________________________________________________________________ > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. > http://join.msn.com/?page=features/virus > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
