KnowCardPython · Sockets & Networking
Why wrap a socket in with socket.socket(...) as s: instead of just assigning it?
Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.
More in Sockets & Networking
You need a network protocol that guarantees every byte arrives, in order, with no loss. Which socket type do you create, and what do you give up vs the alternative?
On a TCP server you call s.accept(). Which socket do you then use to call recv/send with the client?
What is the correct order of TCP server calls before you can talk to a client, and what does each step do?
What does this client snippet do wrong?
```python
s = socket.create_connection(
(ip, 50000))
s.send("hello")
```
A peer sends exactly 1000 bytes in one send. Your TCP code does data = conn.recv(1024). Is data guaranteed to be all 1000 bytes?
In a TCP receive loop, how do you detect that the peer closed the connection?
```python
while data := conn.recv(1024):
...
```
Start learning today
Free to start — download the app or use it in your browser.