This project is read-only.

Proxy cross reference with SuperSocket.ClientEngine

Sep 9, 2015 at 5:11 PM
Edited Sep 9, 2015 at 5:19 PM

I am trying to configure a proxy to my web socket object, and found this code on the web as a sample:
var proxy = new HttpConnectProxy(new IPEndPoint(IPAddress.Parse(proxyConfiguration.Address), proxyConfiguration.Port));
_webSocket.Proxy = (SuperSocket.ClientEngine.IProxyConnector)proxy;
Problem is: if I don't link the SuperSocket.ClientEngine library, it does not recognize HttpConnectProxy. And if I do, it tells me there are 2 references of IProxyConnector: one in WebSocket4Net and one in SuperSocket.ClientEngine.

So... How do I handle that? Am I even creating a proxy correctly?

Source of sample:
And I don't like his solution very much.
Sep 20, 2015 at 4:24 PM
You can reference websocket4net directly, because it contains SuperSocket.ClientEngine already.
Sep 21, 2015 at 3:24 PM
websocket4net is already referenced, that's my problem.
The issue is that websocket4net does not recognize HttpConnectProxy, and when I do reference the SuperSocket.ClientEngine, there is a cross reference with websocket4net on IProxyConnector.
Sep 22, 2015 at 2:30 AM
You need reference an extra assembly SuperSocket.ClientEngine.Proxy.