Thread: Write permissions on root folder - good or bad?

I agree with you Mark, especially on debugging - and I do use .NET rewrite functionality myself on my sites - but I do know somebody that has a very busy site and is using ISAPI_Rewrite and they've had no problems, not to say there won't be - just that it has been stable for them. It'd also easier to manage non .net files with ISAPI_Rewrite, as you don't have to setup wildcard mapping, or mapping ext's to .net etc.

A well-written ISAPI filter should scale a lot better than an ASP.NET solution I would think, but I don't think out and out performance is an issue for the OP as he's on a shared hosting account AFAIK.

The other issue is whether the host will install an ISAPI filter for the OP -- unlikely I'd guess.

Originally Posted by TDMWeb

A well-written ISAPI filter should scale a lot better than an ASP.NET solution I would think, but I don't think out and out performance is an issue for the OP as he's on a shared hosting account AFAIK.

The other issue is whether the host will install an ISAPI filter for the OP -- unlikely I'd guess.

Indeed, therefore writing it in .net would make the whole thing more portable as well, rather than being tied to a host that would support the isapi filter for you.

I wouldn't recommend it, intresting though.

ISAPI_ReWrite performs well we don't have anyone that generates over 1.5gb of logs per day but we do host some exceptionally busy php sites that use various shopping carts and isapi_rewrite.

It can be done in .net not sure on the performance difference though.

You can debug your .htaccess config and do tests etc directly on the server plus ISAPI_ReWrite has a full debug log that logs everything if needed so you can track down issues with a bit of work. We have done this a couple of times for clients and 3rd partys who have had issues. To date i've only every found 1 issue in isapi_rewrite vs mod_rewrtie for apache which they fixed within 9 days.