The "sender" parameter in the callback function will be the object that was
used to generate the original request (such as an HttpWebRequest), so you
can figure out what it is at runtime and then cast it to the appropriate
type.
From there, you can implement some branching logic based on the RequestUri
or something that applies different policies to different hosts. I think
that will get you what you want.
Joe K.

Signature
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
> Hello,
>
[quoted text clipped - 46 lines]
>
> Tibo
letibal@gmail.com - 30 Jan 2007 10:10 GMT
Hi Joe,
I thought it would have been possible to associate the callback
function with a specific HttpWebRequest object (like it is possible
with an SslStream(stream, bool, callback)). The approach you describe
will work, but from a design point of view, keeping everything
seperate would have suited me better.
Once again, thanks Joe for your useful comments.
Tibo
On Jan 29, 4:45 pm, "Joe Kaplan"
<joseph.e.kap...@removethis.accenture.com> wrote:
> The "sender" parameter in the callback function will be the object that was
> used to generate the original request (such as an HttpWebRequest), so you
[quoted text clipped - 62 lines]
>
> > Tibo