Mercurial > public > mercurial-scm > hg-stable
diff mercurial/wireprotoserver.py @ 37058:61393f888dfe
wireproto: define and implement responses in framing protocol
Previously, we only had client-side frame types defined. This commit
defines and implements basic support for server-side frame types.
We introduce two frame types - one for representing the raw bytes
result of a command and another for representing error results.
The types are quite primitive and behavior will expand over time.
But you have to start somewhere.
Our server reactor gains methods to react to an intent to send a
response. Again, following the "sans I/O" pattern, the reactor
doesn't actually send the data. Instead, it gives the caller a
generator to frames that it can send out over the wire.
Differential Revision: https://phab.mercurial-scm.org/D2858
author | Gregory Szorc <gregory.szorc@gmail.com> |
---|---|
date | Wed, 14 Mar 2018 13:57:52 -0700 |
parents | e7a012b60d6e |
children | 861e9d37e56e |
line wrap: on
line diff
--- a/mercurial/wireprotoserver.py Wed Mar 14 13:32:31 2018 -0700 +++ b/mercurial/wireprotoserver.py Wed Mar 14 13:57:52 2018 -0700 @@ -493,15 +493,20 @@ rsp = wireproto.dispatch(repo, proto, command['command']) - # TODO use proper response format. res.status = b'200 OK' - res.headers[b'Content-Type'] = b'text/plain' + res.headers[b'Content-Type'] = FRAMINGTYPE if isinstance(rsp, wireprototypes.bytesresponse): - res.setbodybytes(rsp.data) + action, meta = reactor.onbytesresponseready(rsp.data) else: - res.setbodybytes(b'unhandled response type from wire proto ' - 'command') + action, meta = reactor.onapplicationerror( + _('unhandled response type from wire proto command')) + + if action == 'sendframes': + res.setbodygen(meta['framegen']) + else: + raise error.ProgrammingError('unhandled event from reactor: %s' % + action) # Maps API name to metadata so custom API can be registered. API_HANDLERS = {