Ok, unless there are objections the classes will be renamed to - ResponseHeaders - RequestHeaders, and - Parameters
respectively. I will also create a specialised dictionary that can hold a sequence of strings as suggested by Greg and use this as the basis of the request headers and parameter classes. It will probably be Sunday before I get chance to make these changes now due to my hectic social life ;) so there's still time for more thoughts/comment. Cheers Chris On 22/05/2009, Greg Brown <[email protected]> wrote: >>>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. > > > -- Sent from my mobile device
