Message-ID: <01BE1701.9D7EEDA0@marketing.aart.ch> From: Henning Timcke <email@example.com> To: "'Warner ten Kate'" <firstname.lastname@example.org> Cc: www-tv <email@example.com> Date: Mon, 23 Nov 1998 16:52:10 +0100 Subject: AW: AW: URL: Background and Requirements Hello Warner What is your answer to the URL's on tape ? regards Henning -----Ursprüngliche Nachricht----- Von: Henning Timcke [SMTP:firstname.lastname@example.org] Gesendet am: Dienstag, 3. November 1998 19:06 An: 'Warner ten Kate' Cc: www-tv Betreff: AW: AW: URL: Background and Requirements Okay, please tell me more: store locally on tape ? How will the extra-information be stored that tells at what time on the tape the URL is ? Do you intend to use diffrent methods as in HTTP ? I propose to use XML to handle the hooks neccessary. Time Code could be used as is and another *Time* Code should be developed: topology relevant time for download. Henning -----Ursprüngliche Nachricht----- Von: Warner ten Kate [SMTP:email@example.com] Gesendet am: Dienstag, 3. November 1998 18:49 An: Henning Timcke Cc: www-tv Betreff: Re: AW: URL: Background and Requirements Henning Timcke wrote: > > E.g in HTML there is a Meta Tag that solves the problem of accuracy of the document. <DEFANGED-META CONTENT="no-cache">. A document that is not cached is always requested from it's absolute URL and not from the cache, the local copy. That solves the problem by preventing it: do not (use) cache. In our case this is not a satisfying solution. Our content encompasses Audio/Video material, that users really want to store locally (VCR). Warner.