Waiting retrieves a long-running operation by keeping a client request open until the service marks the operation complete. It favors immediate notification over repeated client requests, while leaving connection management to the API service. section 10.3.3
Compared with polling, waiting:
- Avoids repeated status requests that may produce no update. section 10.3.3
- Reports completion as soon as the service knows the result. section 10.3.3
- Requires a long-lived client-to-service connection. section 10.3.3
Waiting for chat-room creation
Create a chat room, then call WaitOperation with the returned operation ID. When the operation completes, return its ChatRoom result instead of repeatedly calling GetOperation.
