the reference to the document() XSLT function is a great example of what I'd like to do.
-- David B. Bitton [EMAIL PROTECTED] www.codenoevil.com Code Made Fresh Daily™ ----- Original Message ----- From: "Marsh, Drew" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 10, 2002 1:00 PM Subject: Re: custom URL protocol handler > David B. Bitton [mailto:[EMAIL PROTECTED]] wrote: > > > Now, I've seen from the original postings, that I need to > > implement two classes that inherit from WebRequest and > > WebResponse. Where my question lies, is two fold. First, > > does anyone have a sample if this being done? > > There are a couple of samples floating around. I don't have any links off > the top of my head, but you can start by searching gotdotnet.com. i'll see what i can find. thanks. > > > And second, > > once I have these classes, how are they known to be called > > when I create the WebClient() object? > > The WebClient uses WebRequest.Create() to resolve the contents of any uri > you hand it. The WebRequest architecture will then search through the > plugged in protocols (configured via the .config files) for one that matches > the scheme of the uri. Once it finds it, it will instantiate it, pass it the > uri, then return it to the caller of Create (WebClient in this case). The > WebClient then interacts with it through the abstract WebRequest interface > to retrive the resources. ok, so it has to be "hooked up" via a reference in a .config file. Would that be the infamous AppConfig file, or the even more dreaded manifest file? > > HTH, > Drew > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
