Re:WebTCP: Making TCP Connections From Browser
by yankoff on Wednesday November 28, 2012 @05:48PM
(#4845225)
Well, you didn't read the post apparently and only a title :(
[ Parent
| on HN ]
Re:WebTCP: Making TCP Connections From Browser
by chewxy on Wednesday November 28, 2012 @05:53PM
(#4845251)
I actually did. I was quite interested in the redis example. For about 10 seconds, which I then went "wtf is this useful for?"
We really need to stop reinventing the wheel
Re:WebTCP: Making TCP Connections From Browser
by yankoff on Wednesday November 28, 2012 @05:54PM
(#4845258)
What would you use to achieve the same thing with Redis?
Re:WebTCP: Making TCP Connections From Browser
by sebastianmck on Wednesday November 28, 2012 @06:01PM
(#4845294)
The XY Problem http://www.perlmonks.org/index.pl?node_id=542341
Re:WebTCP: Making TCP Connections From Browser
by lttlrck on Wednesday November 28, 2012 @06:43PM
(#4845484)
REST is far more appropriate for databases.
Pub/sub is well catered for by socket.io (websockets).
This glue belongs on the server.
If I did need arbitrary TCP connections my first thought would be a websocket proxy...
Re:WebTCP: Making TCP Connections From Browser
by chewxy on Wednesday November 28, 2012 @06:03PM
(#4845301)
I wouldn't. I'd make a HTTP call to the server, and let the server handle it. (i.e. your "what's so different from the backend method")?
Re:WebTCP: Making TCP Connections From Browser
by yankoff on Wednesday November 28, 2012 @06:12PM
(#4845342)
Yep, and i wrote about differences to such approach in the post. Don't get me wrong, this is definitely a hack, I'm not saying people should stop doing it the old way.
Re:WebTCP: Making TCP Connections From Browser
by chewxy on Wednesday November 28, 2012 @06:15PM
(#4845354)
Likewise. While I appreciate the concept of a bridge (I'm a strong believer that the fastest app is the app that does practically nothing at all, and I can see the benefit of using a TCP-bridge like thing to make something faster), I just think we should not be reinventing the wheel.
That is to say, if you need a TCP connection to any server, you probably should not be implementing it over HTTP (well, this is where definitions get difficult, since you know, HTTP is technically TCP. Fuck)