[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: hrm
> I'd go a step further and link cord types explicitly to protocol
> names. I.e., just as you can only create messages that have a prefix
> which you own (say, "dns-com-att-research-twin-edit"), you can only
> create cord names that have a prefix which you own. note that this
> can be a non-strict prefix, e.g., if there's a "twin" protocol, we
> could have a "twin" cord type and a "twin" message.
ok, i'd like to pretty much say, then, something along the lines of
'the same rules apply to cord names as protocol names', is this ok
with everyone?
dk
- References:
- hrm
- From: Dave Kormann <davek@research.att.com>
- Re: hrm
- From: Erik Ostrom <eostrom@research.att.com>