Add web socket support

[devigned]

Expected Behavior

Should be able to connect to Event Hubs via web sockets rather than over the standard AMQP ports to better support common open ports.

Actual Behavior

The library only supports common AMQP ports.

[sopatwar]

Any approximate ETA for this enhancement ?

Thanks,
Sourabh

[devigned]

This is something I've wanted to add for a while. I'll see if I can get you a branch to test out late this week or early next.

[sopatwar]

@devigned Great!
Will wait for your update.

Thanks,
Sourabh

[sopatwar]

@devigned
Do you have any update for me ?

Thanks,
Sourabh

[devigned]

Sorry to say that I haven't been able to get to this feature due to other work priorities. I will try to get it out as soon as possible.

[devigned]

Sorry for the long wait, but here's a branch with WSS support. I'll be adding an example shortly and more tests shortly.

[sopatwar]

@devigned Thanks for committing this!
Will wait for #124 to get sorted out and then test this out.

-Sourabh

[devigned]

@sopatwar, I'm hoping #124 gets sorted out quickly, but if you use dep or vgo you should be able to use the SDK without the delay of waiting on #124.

[sopatwar]

@devigned
I need to use the new web sockets API from on-prem (going through IT-managed HTTP proxy)
The golang websocket package cannot handle this.
An alternative library suggested in the godoc is gorilla
Reference godoc: websocket

Is it feasible to make the Azure API configurable to use gorilla web socket as an option?
This would enable using web socket via http proxy.

Thanks,
Sourabh

[devigned]

I was toying with the idea of allowing consumer of the library to supply their own net.Conn. That way consumer can be as flexible as they wish. Thoughts?