[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MCP 2.1
> as for the comment about multiple identical keywords: i'm going to by
> fiat say that you take the first one and throw away the rest, and that
> compliant implementations should never ever ever ever send duplicate
> keywords. any objections or alternative suggestions?
I suggest you take the last one and throw away the rest. That way you
can but the key/value pairs in a hash table and the last one you put
there is the one you want.
John
- References:
- MCP 2.1
- From: "John D. Ramsdell" <ramsdell@linus.mitre.org>
- MCP 2.1
- From: Dave Kormann <davek@research.att.com>