~ if the headers are being parsed anyway as part of the initial client-server negotiation, it would be great if the most amount of juice is squeezed at once as part of the parsing, instead of then figuring things out (-parsing again- (sometimes repeatedly in code I have read)) the result of Header.getValue() ~ There are a number of issues with that (re)implementation I am sure you will see, for example, if for some reason some server's changes have been made and the set parsing context does not match the response headers a NotMatchedHeadersParsingContextException should be thrown, but if the extra Header Names of the bag if not matched just a warning should be logged ~ lbrtchx
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
