On Sat, 25 May 2002 11:25:25 -0500, Reggie Burnett <[EMAIL PROTECTED]> wrote:
>Yes I could do that. I'm sorry I'm being a bit stubborn on this issue >but I was really hoping to find a solution that would properly integrate >into the framework. The documentation really doesn't say where the >RegisterPrefix call should be issued. It feels better to me to not >require the extra step by the user, but perhaps that is what MSFT was >expecting. Reading the docs today suggests that it should be enough for the client to specify an IWebRequestCreate implementing class in his application configuration file? Or maybe even in the machine.config, somewhere? This is what the runtime does for HttpWebRequest, HttpsWebRequest, and FileWebRequest. <configuration> <system.net> <webRequestModules> <add prefix="reggieUrlPrefix" type="Burnett.reggieWebRequestCreator" /> <!-- modelled after the machine.config entry: <add prefix="http" type="System.Net.HttpWebRequestCreator" /> --> </webRequestModules> </system.net> </configuration> This way the WebRequest class should execute your WebRequest.Create function. I know this is not a general applicable solution, but it might be the solution work for the WebRequest.Create() problem. Bye now, Robert You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
