4 ms·
Your first point, this is just the JS implementation of the socket API. So yes, Chrome can accept a connection and send it back. 2nd point, yes, as long as yo
by kinlan 14y ago
Your first point, this is just the JS implementation of the socket API. So yes, Chrome can accept a connection and send it back.
2nd point, yes, as long as you bind it to your IP address.
3rd point. Honestly not sure.
- th0ma5 14y agoI would say probably not on #3 ... however, given the general NAT concept and such, having an outgoing connection could poke the hole, but this isn't how a listening service usually works, so it would require something else. However, once the session is negotiated, then HTTP (in theory) should work, although it is stateless at that level, but anyway, this is all a lot of bother because at this point you should go ahead and do something that's less of a kludge since you're already doing NAT traversal.
- Evbn 14y agoJS implementation of the API, or JS shim over the system API?