The overhead should be in milli- or micro-seconds for an HTTP Handler to
take "friendly URLs" and turn them into a non-friendly path. I have only
played with this and not hammered at scale (and am no longer working on the
project), so I cannot give you figures, but the Handlers occur as part of
the ASP.NET process, and incur almost no overhead. I am sure you could write
an inefficient method that makes this statement incorrect. :-)
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
|
*************************************************
<thoeonewrote in message news:ek**************@TK2MSFTNGP03.phx.gbl...
Hi,
Anyone have any experience with url rewriting on asp.net and performance
issues. I want to know how much of a lost in performace(percentage wise)
if i use Context.RewritePath() function to make a friendly url. Any
experience or links to benchmarks is appreciated.
#source: http://www.codeverge.net