Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add opaque response type to MsgReplyObjIds #28

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nbacquey
Copy link
Member

No description provided.

\item [\argfont{objectIds}] An opaque type returned by the server when asked for object ids.
It is not explicitely a list of $\argfont{id}$, because the server may want to add metadata to the ids,
and/or run a compression scheme to limit the size of its response.
\item [\argfont{responseToIds}] A function with type $\argfont{obejctIds} \rightarrow [\argfont{id}]$.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be generic and have a chance to cover Tx-Submission, shouldn't it then be

objectIds -> [(id, size)]

?

Also typo: s/obejct/object/


\item [\MsgRequestObjs{} {($[\argfont{id}]$)}]
The client requests objects by sending a list of object ids.
The total size of the corresponding objects MUST not be bigger than the size limit in bytes.
\niols{Or maybe a bit less; should we take into account the size of the boilerplate?}

\item [\MsgReplyObjs{} {($[\argfont{object}]$})]
\item [\MsgReplyObjs{} {($[\argfont{object}]$)}]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact, I'd even go for $( ... )$ to get the math parentheses. But then we should probably go for $\MsgReplyObjs{} ( ... )$ with a macro to create the right spacing after \MsgReplyObjs with eg. \mathop. Let's no go there :p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants