You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
iprotoRelated to the iproto protocolreference[location] Tarantool manual, Reference partserver[area] Task relates to Tarantool's server (core) functionality
In PR #2918 , @ locker requested a documentation improvement about IPROTO requests for stream transactions:
We have a separate entry for each IPROTO command (IPROTO_SELECT, IPROTO_REPLACE, etc) with the description of header and data fields, but not for IPROTO_BEGIN, IPROTO_COMMIT, IPROTO_ROLLBACK - those commands are clustered together in one section, but they are no worse than other commands so why would we want to treat them in a different way? If I developed a connector to Tarantool, I'd prefer all IPROTO commands and their arguments to be listed explicitly.
Definition of done
Add a section for IPROTO_BEGIN
Add a section for IPROTO_COMMIT
Add a section for IPROTO_ROLLBACK
The text was updated successfully, but these errors were encountered:
p7nov
added
reference
[location] Tarantool manual, Reference part
server
[area] Task relates to Tarantool's server (core) functionality
iproto
Related to the iproto protocol
3sp
labels
Jun 6, 2022
iprotoRelated to the iproto protocolreference[location] Tarantool manual, Reference partserver[area] Task relates to Tarantool's server (core) functionality
Uh oh!
There was an error while loading. Please reload this page.
Product: Tarantool
Since: 2.10
Audience/target: iproto devs
Root document: https://www.tarantool.io/en/doc/latest/dev_guide/internals/box_protocol/
SME: @ locker
Details
In PR #2918 , @ locker requested a documentation improvement about IPROTO requests for stream transactions:
Definition of done
The text was updated successfully, but these errors were encountered: