On Tue, 7 Jul 2009, Alex Rousskov wrote:
>
> What is the motivation behind adding more ports?
WebSocket is its own protocol, so the "right thing" to do is to use new
ports. However, WebSocket can be sent over 80 or 443 quite happily.
> Can websocket use port 80 (without CONNECT) and port 443 (with CONNECT)?
Yes.
> I have noticed there is something about the Upgrade header in the
> websocket draft so perhaps that mechanism can be polished to implement a
> proper protocol switch? Or is that too late?
It actually does support a true HTTP Upgrade also, so that people who are
already using ports 80 or 443 for HTTP can still use WebSocket if they are
able to make their servers handle the protocol upgrade.
Cheers,
-- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'Received on Mon Jul 13 2009 - 07:41:26 MDT
This archive was generated by hypermail 2.2.0 : Mon Jul 13 2009 - 12:00:04 MDT