OpUrl - ISAPI URL Rewrite
FAQ
 What impact will OpUrl have on the security of the server?
 In a word: very little!
In normal use the filter doesn't read or write to any files, except it's
configuration and log file when it's first starting up. It therefore doesn't
require any changes to the existing security settings on files and directories.
The filter can also be installed solely on the web site on which it's required - leaving
other virtual roots/web sites on the IIS server untouched.
What impact will OpUrl have on the performance of the server?
In a word: very little!
It's written in C++ and uses a very high performance mattern patching algorithm.
Statistics on the regex++ site state that a 65 character string is matched against a relatively complex pattern in 127ms on a P90.
In the future I might produce some timings on the Dual PIII 800's running the average web server nowadays!
As you can see, compared to the other overheads involved in serving up web-pages, the 'cost' of OpUrl in terms of processing power is minimal.
Also, as mentioned before, there is no file access so there should be no I/O bottlenecks.
Why do the configuration and log files live in the System32 directory?
This is because the files are written and read using the current directory.
Because the filter runs as part of IIS, which itself lives in System32, that's where the files are.
If you'd rather this was changed, let me know and we'll see what we can do.
What about per-server licensing? Do I have to buy copies for my development machines too?
A. No. You'll need to buy a copy for each production server on which OpUrl will be run.
You can install copies on development and test machines as required.
These are generally speaking boxes that aren't accessible to the public, or whoever the 'end users' of the site are.
Is OpUrl being used on any commercial sites?
Yup. At the minute the list is fairly small, but growing. More sites will be added soon.
To see OpUrl in action, you can take a look at: http://www.nubold.com
|
