What is a request-response pair called?
HttpNamingHttp Problem Overview
For example in HTTP you send a request and receive a response; is there a noun that describes that request-response pair?
I'd thought of "dialog" or "conversation" however those imply multiple request-response pairs, whereas I'm looking for a word that indicates exactly one.
The reason for asking is that I need to name an object which encapsulates the details of both, and RequestResponse
seems fairly lame.
Http Solutions
Solution 1 - Http
- RFC2616 calls it an Exchange.
- Wireshark and HTTPNetworkSniffer call it a Request/Response.
- Fiddler calls it a Session.
- Charles calls it a Sequence.
- HTTP Scoop calls it a Conversation.
- Other vocabulary includes: Message, Transaction, Communication.
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.
Solution 2 - Http
How about "exchange"?
Solution 3 - Http
RequestResponsePair
sounds like it does exactly what it says. And that's invaluable, I find.
Solution 4 - Http
Interaction
Solution 5 - Http
I'd use Message or Transaction
Solution 6 - Http
Transceival
or ServiceCall
might work.
Solution 7 - Http
HttpRoundTrip
- inspired by Jeff Atwood in this blog post
Solution 8 - Http
Fiddler calls it a Session.
Solution 9 - Http
OpenRasta used "communication" for the request/response couple.
Solution 10 - Http
In my particular case I consider calling it a Connection
. When you send a HTTP request, you're basically establishing a connection with some endpoint.
At least one reason why I dislike it is that similar to Session
, one can assume there is some activity at the moment happening, which may or may not be true.
Background: I need to log all interactions with third-party service.
P.S. IMHO, Exchange
is the best among others. It sounds more abstract.
Solution 11 - Http
What about ServiceConversation
Solution 12 - Http
what about RequestResponseContext
?