fish <[EMAIL PROTECTED]> writes: > On 2 Nov 2002, Chris Dennis wrote: > > > For example, you can't have > > > > SSK@zzz > > Document > > Redirect.Target=CHK@xyz > > Info.Format=text/html > > EndPart > > CHK@xyz > > The actual data > > > > Instead, you should use > > > > SSK@zzz > > Document > > Redirect.Target=CHK@pqr > > EndPart > > CHK@pqr > > Document > > Info.Format=text/html > > End > > The actual data > > > > Or have I misunderstood the spec? > > Either will work. Whch you prefer depends on whom you ask.
But for the first alternative, accessing CHK@xyz directly will not give you a proper MIME type, while CHK@pqr in the second one will. As referencing a CHK directly is sometimes preferable, the second alternative looks more promising to me. Timm Murray <[EMAIL PROTECTED]> writes: >>> It was during the 0.3 era when it was realized that (surprise!) >>> inserting different metadata would change the CHK value. This >>> would often happen if (for example) two people inserted the same >>> thing using FProxy, but one used "use file extention" and the >>> other set the MIME type manually. Since the same data is >>> *supposed* to colide when you're using a CHK, it was decided that >>> it would be best to entirely disallow metadata with CHKs. Do we really need to work around these insertion mistakes? In a way it's /not/ the same data if it has a different MIME type. -- Robbe
signature.ng
Description: PGP signature
