Re: "resolution mechanism"

> Pretend HTTP didn't exist, and that all we knew was that we wanted a 
> protocol that could be used to resolve URI, while keeping in mind that 
> it is an error to try to build this protocol to only accept some URI, 
> and not all.

depends on what you mean by "resolve".  if you mean "ask for metadata",
then I'd say it should look a lot like RC.  if you mean "get", where
the payload is likely to be long and best transferred without loss,
then HTTP is not a bad approximation.  but IMHO "get" is best implemented
in different protocols for different kinds of media - I don't think it's
a good idea to try to make a one-size-fits-all get.

Keith

RC = draft-ietf-rescap-rc-01.txt

Received on Friday, 12 April 2002 20:30:13 UTC