[Mono-dev] Patch for HttpRuntime and HttpServerUtility to bring API in sync with .NET 2.0 SP2

Marek Habersack grendel at twistedcode.net
Thu Sep 24 04:56:04 EDT 2009


Nick Berardi wrote:
> Hello group,
Hello,

> This is my first time submitting a patch.  So if anything I have done is 
> out of the norm, please let me know so that I can correct it.  
> 
> There are two API's related to IIS 7.0 that were added as part of the 
> .NET 2.0 SP2 release that I need supported for an Open Source project 
> that I work on (http://urlrewriter.codeplex.com). 
>  (http://urlrewriter.codeplex.com/WorkItem/View.aspx?WorkItemId=7187)
> 
> The patch that I am submitting is for the following APIs:
> 
>     * HttpRuntime.UsingIntegratedPipeline { get; }
>     * HttpServerUtility.TransferRequest(string,[bool],[string],[NameValueCollection])
> 
> Since both of these API's are IIS 7.0+ specific and that they require 
> the Integrated Pipeline to function.  I have the first property 
> UsingIntegratedPipeline always returning false, since it is currently 
> impossible to put Mono in to the core of IIS 7.0, so Integrated Pipeline 
Technically Mono has always been using what IIS 7 calls "integrated pipeline" - there are no plans 
to make Mono run in the IIS core, so we should try to implement whatever functionality makes sense 
in Mono context without looking whether or not it works in this or that IIS mode. I'd say 
UsingIntegratedPipeline could return 'true' without harm.

> can't currently be supported.  So I hoped to achieve the 2nd best option 
> of API completeness.  The second method TransferRequest relies on the 
> Integrated Pipeline so again it will not be supported.  So I have the 
> method just throwing the publically available exceptions shows on MSDN. 
>  This second method will always throw PlatformNotSupported, for API 
> completeness with the .NET 2.0 SP2 framework.
This method, as well, can be implemented to perform its function on Mono just fine. If you feel like 
giving it a try, I'd welcome a new patch which implements it. If not, I will accept the patch as it 
is now and implement the API fully at some point.

> Please let me know what the next steps are or if there is anything that 
> I need to change in order to get this patch moved into production.
> 
> Thanks,
> Nick

best regards,

marek


More information about the Mono-devel-list mailing list