>Just a thought, but the same thing technically applies to request headers >(aka RequestProperties) and request parameters (aka Arguments) as well, i.e. >it's perfectly valid to have multiple values for the same name...
True. Dictionary#get() can only return a single type, so ResponsePropertiesDictionary has to implement Dictionary<String, ImmutableList<String>>. However, put() can support overloads. We could potentially add put(String, Sequence<String>) methods to ArgumentsDictionary and RequestPropertiesDictionary to support this feature. >In fact - I think the names of these classes are misleading - why not just >stick with what people are generally used to? >e.g. >ResponseProperties should really really ResponseHeaders >RequestProperties should really be RequestHeaders >Arguments should really be RequestParameters The names are consistent with their .NET equivalents, as I recall. I find the naming to be fairly intuitive, but I'm not opposed to changing it. What do others think?
