>you can have multiple headers with the same name, e.g.
>
>Set-Cookie: name=MyCookie; value=Some value
>Set-Cookie: name=AnotherCookie; value=666
I thought about that when writing the Query class initially, but I went with
the simplified approach because I couldn't think of many use cases for multiple
response headers with the same name. I forgot about the cookie case, though,
which is pretty important. I think your suggestion is good, though I would
change String[] to a Sequence<String> since we generally use sequences in place
of arrays throughout the API, and we'll probably want it to be read-only. Maybe
something like this:
public final class ResponsePropertiesDictionary
implements Dictionary<String,
pivot.collections.immutable.ImmutableList<String>>, Iterable<String> { ... }
Greg
