search

CSCG / shellinabox

Automatically exported from code.google.com/p/shellinabox
Other
0 stars 0 forks source link

Feature Request: Use WebSockets instead of AJAX #111

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
WebSockets provide for a more efficient & more natural way of implement 
client/server communication.

Original issue reported on code.google.com by lpsan...@gmail.com on 18 Jan 2011 at 9:56

GoogleCodeExporter commented 9 years ago 
Completely agree, this would be an awesome feature.

Original comment by chre...@gmail.com on 21 Jan 2011 at 3:38

GoogleCodeExporter commented 9 years ago 
Probably good to use something like socket.io so those using old versions of 
browsers can still use shellinabox

Original comment by chre...@gmail.com on 21 Jan 2011 at 3:44

GoogleCodeExporter commented 9 years ago 
Great idea -- perhaps it could gracefully downgrade to  AJAX

Original comment by callan.bryant@gmail.com on 9 Apr 2011 at 11:41

GoogleCodeExporter commented 9 years ago 
Patches welcome.

Original comment by beewoo...@gmail.com on 31 Mar 2012 at 10:24

GoogleCodeExporter commented 9 years ago 
I disagree, I think shellinabox should push foward using AJAX, Websockets gets 
blocked by proxy servers and firewalls often. Since shellinabox is mostly used 
in draconian environments we need too make sure it is optimized for those use 
cases.

Original comment by MichaelC...@gmail.com on 14 Sep 2012 at 2:15

GoogleCodeExporter commented 9 years ago 
Web sockets shouldn't get blocked by firewalls on ports 443 & 80 unless they're 
doing multi-protocol packet inspection. Some older proxy servers will have 
issues with the http upgrade header and forwarding the connection but that was 
fixed in the protocol more than a year ago. The suggestion to use socket.io on 
the server side & client would enable graceful fall back on a large population 
of browsers going back several years.

Original comment by lpsan...@gmail.com on 14 Sep 2012 at 4:22