>>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
OK, after thinking on it for a bit, I like "RequestHeaders" and "ResponseHeaders" but "RequestParameters" seems a bit verbose. What about just "Parameters"? The terminology we're familiar with is "query string parameters" - "query" is implied by the class name and "string" is implied by the fact that we use a URL to pass them, so "parameters" might be sufficient.
