Updated Branches: refs/heads/cassandra-1.2.0 01c9e1050 -> 5ecb91ff4
Make it clear you don't have to use the 128 stream id if you don't have to Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5ecb91ff Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5ecb91ff Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/5ecb91ff Branch: refs/heads/cassandra-1.2.0 Commit: 5ecb91ff46a270402fa69fe05caa7d4ba72126db Parents: 01c9e10 Author: Sylvain Lebresne <[email protected]> Authored: Tue Nov 13 11:49:20 2012 +0100 Committer: Sylvain Lebresne <[email protected]> Committed: Tue Nov 13 11:49:20 2012 +0100 ---------------------------------------------------------------------- doc/native_protocol.spec | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cassandra/blob/5ecb91ff/doc/native_protocol.spec ---------------------------------------------------------------------- diff --git a/doc/native_protocol.spec b/doc/native_protocol.spec index 9c27bb3..4c31ca8 100644 --- a/doc/native_protocol.spec +++ b/doc/native_protocol.spec @@ -132,9 +132,11 @@ Table of Contents respond to. As there can only be 128 different simultaneous stream, it is up to the client to reuse stream id. - Note that clients are free to use the protocol synchronously (i.e. wait for + Note that clients are free to use the protocol synchronously (i.e. wait for the response to REQ_N before sending REQ_N+1). In that case, the stream id - can be safely set to 0. + can be safely set to 0. Clients should also feel free to use only a subset of + the 128 maximum possible stream ids if it is simpler for those + implementation. 2.4. opcode
