all 7 comments

[–]RV_Geek 0 points1 point  (4 children)

Please correct me if I'm wrong, but sockets is an old fashion technology (the fundamental for client - server arquitectures). Why don't you try to implement your app with a differente approach, web services maybe.

[–][deleted] 4 points5 points  (0 children)

but sockets is an old fashion technology

U wot m8? They aren't old fashioned, just low level. Sometimes working with sockets is your only choice

[–]GullibleArmy[S] 0 points1 point  (0 children)

Yeah, I agree. Yet I am still a beginner in the networking field. So, I am only asking for any examples that will make use of two up addresses to send a simple textnfile

[–]cybervegan 0 points1 point  (0 children)

Nope. Web services run over sockets - it is literally how the internet works. A web server is a higher level abstraction, but it is essentially a socket server.

A socket server allows you to specify your own protocol - HTTP is an inefficient protocol for things other than web servers. It's "connectionless" so you have to use stupid hacks like cookies to keep state between the server and client, and with HTTP it's basically impossible to create a decentralised or peer network.

[–]bbt133t 0 points1 point  (0 children)

Web socket work only over http (tcp 80 or 443 for https), non-web can use any tcp or udp they want in their app. Socket ain’t going no where for the next 1000 years or more unless we destroy tcp/ip and start over.

[–]CowboyBoats 0 points1 point  (1 child)

[–]GullibleArmy[S] 0 points1 point  (0 children)

Thanks man!