A73: Transport Selection #399
Conversation
A73-transport-selection.md
Outdated
| (pending) [Call Semantics | ||
| Specification](https://github.com/grpc/grpc/pull/15460) and hide HTTP/2 | ||
| semantics and grpc's wire protocol semantics. | ||
| 1. Stream APIs should support object-based messages to facilitate an in-process |
There was a problem hiding this comment.
Based on the end, it seems you're expecting to make a copy here. I'd suggest mentioning copying objects as the alternative to serialize+deserialize. Otherwise it isn't really clear what you're talking about. On the face of it it looked like you'd just pass the object from client to server, but that is fundamentally broken unless the objects are immutable.
A73-transport-selection.md
Outdated
| clients and servers. The exact details will be left up to gRPC implementations | ||
| to decide; only the high-level method is included in this design. | ||
|
|
||
| Some additional design goals of this proposal: |
There was a problem hiding this comment.
This is awkward. It is in the proposal section, and defines a mix of goals and design choices. I think "goals" isn't the right word here, as these are part of the proposal itself. Goals shouldn't be in "Proposal" anyway.
There was a problem hiding this comment.
Moved into a sub-section about transports.
A73-transport-selection.md
Outdated
| clients and servers. The exact details will be left up to gRPC implementations | ||
| to decide; only the high-level method is included in this design. | ||
|
|
||
| Some additional design goals of this proposal: |
There was a problem hiding this comment.
Moved into a sub-section about transports.
A73-transport-selection.md
Outdated
| (pending) [Call Semantics | ||
| Specification](https://github.com/grpc/grpc/pull/15460) and hide HTTP/2 | ||
| semantics and grpc's wire protocol semantics. | ||
| 1. Stream APIs should support object-based messages to facilitate an in-process |
No description provided.