Prev: email
Next: Start .NET Web Application Development
From: jim on 29 Dec 2009 05:13
Is there a way to have different webbrowser controls open at the same
time while using a different proxy for each control?

Is it possible to have different webbrower controls in different threads
with each webbrowser control utilizing a different proxy?

From: Gregory A. Beamer on 29 Dec 2009 11:56
jim <jim(a)home.net> wrote in news:7Dk_m.17110$eH1.11813(a)newsfe16.iad:

> Is there a way to have different webbrowser controls open at the same
> time while using a different proxy for each control?
>
> Is it possible to have different webbrower controls in different
> threads with each webbrowser control utilizing a different proxy?

Directly? I don't think so.

The problem here is the WebBrowser control is a wrapper that does not
expose enough.

But it is not all doom and gloom. You can use the other NET classes to
get the HTML from the site and then use ProcessRequest to pull in the
HTML from a stream object. Going this route, you have control over the
proxies used, etc.

Yes, it is more involved, but to me this is a lot like asking questions
about the DataSource control, which wraps (and hides) most of the data
functionality from the developer.

Peace and Grace,

--
Gregory A. Beamer (MVP)

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************
From: jim on 31 Dec 2009 06:48
On 12/29/2009 11:56 AM, Gregory A. Beamer wrote:
> jim<jim(a)home.net> wrote in news:7Dk_m.17110$eH1.11813(a)newsfe16.iad:
>
>> Is there a way to have different webbrowser controls open at the same
>> time while using a different proxy for each control?
>>
>> Is it possible to have different webbrower controls in different
>> threads with each webbrowser control utilizing a different proxy?
>
> Directly? I don't think so.
>
> The problem here is the WebBrowser control is a wrapper that does not
> expose enough.
>
> But it is not all doom and gloom. You can use the other NET classes to
> get the HTML from the site and then use ProcessRequest to pull in the
> HTML from a stream object. Going this route, you have control over the
> proxies used, etc.
>
> Yes, it is more involved, but to me this is a lot like asking questions
> about the DataSource control, which wraps (and hides) most of the data
> functionality from the developer.
>
> Peace and Grace,
>
Thanks for the reply. Any clue as to what .net classes I should start with?

Also, is there a good online reference for finding functionality within
the .net framework's bagillion classes?

Thanks again!
From: Gregory A. Beamer on 31 Dec 2009 11:54
jim <jim(a)home.net> wrote in news:ic0%m.37$Wl3.7(a)newsfe11.iad:

> Thanks for the reply. Any clue as to what .net classes I should start
> with?
>
> Also, is there a good online reference for finding functionality
> within the .net framework's bagillion classes?

Assuming this is all HTTP (working with web sites and web servers) - which
is probably safe considering the web browser control - you start with
HttpRequest and HttpResponse. These are the main wrapper classes for the
WinAPI Internet functionality.

In the docs, start here:
http://msdn.microsoft.com/en-us/library/system.web.aspx

If you want a code project to understand the mechanisms:
http://www.codeproject.com/KB/IP/httpwebrequest_response.aspx

Peace and Grace,


--
Gregory A. Beamer (MVP)

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************
 | 
Pages: 1
Prev: email
Next: Start .NET Web Application Development