Hi,
If you want ultimate control, you can handle all the HTTP request yourself with a custom resource handler. Inside your custom resource handler, you can use whatever means/proxy/cookies as you wish. See here for more information about custom resource handler:
http://www.essentialobjects.com/doc/6/advanced/resource_handler.aspxIf you do not wish to use custom resource handler, you can attach your own cookies by handling the WebView's BeforeRequestLoad event:
http://www.essentialobjects.com/doc/6/eo.webbrowser.webview.beforerequestload.aspxThis allows you to assign cookies to each request.
Proxy settings are global. This is similar to the proxy settings in your "Internet Options" dialog. However since our library is .NET, it is per AppDomain. So you should be able to create multiple AppDomain and use different settings in each AppDomain. There is no way for you to maintain different proxy settings for different WebView instance.
Additionally, you must pay attention to threads when you use WebView. A WebView is associated to the thread in which it is created, thus you can not call any WebView method from any arbitrary thread. This usually is not an issue because the WebView is always used in the UI thread. If you must create the WebView from another thread, you can use this class:
http://www.essentialobjects.com/doc/6/eo.webbrowser.threadrunner.aspxYou can use the ThreadRunner's CreateWebView to create a new WebView in the ThreadRunner's thread (each ThreadRunner object has its own thread), and then use Post or Send method to call methods on that WebView in that thread.
Hope this helps. Please feel free to let us know if you have any more questions.
Thanks!