Menu
TCP/IP uses the client-server model of communication in which a user or machine (a client) is provided a service, like sending a webpage, by another computer (a server) in the network.
HTTP and connections Among the two most common transport protocols on the Internet, TCP is reliable and UDP isn't. HTTP therefore relies on the TCP standard, which is connection-based.
You use a TCP/IP client node in a message flow to create a client connection to a raw TCP/IP socket, and to send or receive data over that connection to or from an external application. The TCP/IP client nodes open a connection to a remote server application that is listening on a TCP/IP port.
Vanilla– the most basic scan; an attempt to connect to all 65,536 ports one at a time. A vanilla scan is a full connect scan, meaning it sends a SYN flag (request to connect) and upon receiving a SYN-ACK (acknowledgement of connection) response, sends back an ACK flag.
I am about to start designing/developing a client-server iOS app. I am leaning towards using HTTP requests to get/post data from/to a server, but want to make sure this is the right decision. What are the benefits of using sockets over http requests. Are sockets faster? One reason I am leaning towards http is that I also want to have a web interface as well as iOS interface. If I create PHP web services that the iOS and web application can both access, then I believe I am reducing development time.
By the way, I have read through these tutorials, which provide some benefits of sockets, but none of the benefits mentioned are necessarily game changers. Except that I don't completely understand what he means by "You can send just the exact data you need to send – making your protocol lean and efficient." Does anyone know what he means here?
Thanks in advance.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With