There\'s one thing I haven\'t found in rfc 2616 and that\'s a \"canonical\" name for a request/response pair. Is there such thing?
4.1 Message Types HTTP me
(answer originally taken from a duplicate question)
I would go for Exchange
or RequestResponse
.
I also went to name it Operation
in my code as I would queue Operations, flush Operations, pause or resume Operations.
Exchanges is nice name, also we can use Connection, Communication or session
The spec calls them "exchanges" (or "request/response exchanges"),
In HTTP/1.0, most implementations used a new connection for each
request/response exchange. In HTTP/1.1, a connection may be used for one or more request/response exchanges.
Transaction, yes, or "A singe HTTP Request consists of one HTTP Request message and one HTTP Response message."