>is there any reason why [HttpMethodBase.setHttp11(boolean)] >should not be public.
Not that I'm aware of. Since it's easier to make a private method public than vice versa, we dropped everything down to the lowest level of accessibility that seemed reasonable. Your example: >Unfortunately silverstream has a bug in how it deals with Http1.1 so we >needed to force >the GetMethod use http1.0. seems like a compelling enough reason to expose it at least as part of the HttpMethodBase interface. (I'm a little suspicious of moving it up to the HttpMethod interface, but that's a different question.) I'd support making it public. >If the setHttp11 is to remain protected is the best solution be to extend >GetMethod, overriding the setHttp11 method with a public >implementation that simply calls the method in HttpMethodBase? That's the only other solution I can think of, and should work without problem, although it's fairly awkward to code and maintain. _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
