Explanation:
HTTP is stateless, meaning it does not maintain session information between requests. Each request is independent .
HTTP follows a requestβresponse model, where the client initiates a request and the server responds. That means communication is always client β server β client, not simultaneous in both directions.
Although newer versions (like HTTP/1.1 with pipelining or HTTP/2 multiplexing) allow more efficient handling, HTTP is still fundamentally half-duplexβitβs not full duplex because only one side can actively send at a time.
Why not the other options?
(A) Stateful β Incorrect. HTTP doesnβt preserve state between requests .
(C) Bidirectional β Incorrect. While data does go back and forth, it's not spontaneous from both ends; the server only responds after a request.
(D) Full duplexβ Incorrect. Only one side transmits at a time; true full duplex (simultaneous two-way communication) is seen in protocols like WebSocket, not HTTP.
So, HTTP is best described as a stateless, unidirectional (half-duplex) requestβresponse protocol.
Answer: (B) unidirectional