3 ms·
A single URI does not name a single piece of data. It doesn't have to; but there's no reason why it couldn't. And there's no reason why a standard couldn't be
by pdonis 13y ago
A single URI does not name a single piece of data.
It doesn't have to; but there's no reason why it couldn't. And there's no reason why a standard couldn't be developed that let the owner of a URI designate that it named a single piece of data that would never change.
Thanks for the links, I'll read them to get a better idea of the proposal.
- mbrubeck 13y ago> And there's no reason why a standard couldn't be developed that let the owner of a URI designate that it named a single piece of data that would never change. Yes, I agree. The "new URI scheme" I suggested in my previous comment is one possible way such a standard might be written. That's just one part of the solution, though; if you want the benefits of getting off of TCP then you also need standards for the new content-centric network layer protocol(s) that will replace it, and you need to implement that in your networks and routers.