Re: Making MGET more GET-friendly?

> I agree the round trip is a cost; I see no evidence to support your
> argument "it is seldom necessary to give descriptions distinct
> identity...".    I need to do it all the time.

We have the same; and

> I think the extra round-trip is worth the cost, and advocate a
> "Metadata-Location" header for information resources, and also a "303

this is very much why we so much like DDDS;

->	go in one step from URI -> Resource OR metadata.

->	One can exist without the other OR vice versa.

->	They can have totally disjoint accessor methods or
	protocols; or multiple; i.e. HTTP for the resource and
	z39.50, soap/lsid or http for the metadata.

Dw