I'm relatively new to web development as a whole, only having started to look at it back in September last year, so bare with me if my question/s seem uninformed.
From what I'm understanding here, a custom Rewrite Engine has been written for use with IIS and that there is also a tool available to convert mod_rewrite rules to the standard used by this Rewrite Engine. With this being the case, what was the reason behind developing a custom Rewrite Engine as opposed to a 'port' of mod_rewrite. It seems like twice as much effort to implement a new system and a conversion/translator tool to convert the Rewrite Rules, as it would have been to use a similar/ the same syntax. Was there some underlying advantage in performance/adaptability in writing a custom system, or perhaps some legal issue with essentially recreating mod_rewrite. Since Apache is undeniably the current de facto standard, it seems odd to expect people to learn a new system / rely on a translation system, if it was possible to simply implement something they are currently used to.
Also I'm not sure it was explicitly asked or addressed, but is there support for per directory changes of other environmental settings, such as access rights, error documents etc which people are so used to using with Apache.