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
And the note regarding references, to be added below the table and the other notes:
*g. {{note|vpack1refs}}VelocyPack offers a value type to store pointers to other VPack items. It is allowed if the VPack data resides in memory, but not if stored on disk or sent over a network.
The text was updated successfully, but these errors were encountered:
Everything you have put there is OK, as far as I see.
So far, there is no Schema-Interface description language.
So far, there are no standard APIs, only a reference implementation. However, other formats say "yes for C++, etc. " here. We might as well say "C++ API reference implementation".
For zero-copy operations, we simply say yes. Not entirely sure what they mean there.
I believe small integers are not zero-copy, because they need to be loaded into a buffer in order to subtract 0x29 or 0x39 respectively to get the actual value.
It deserves to be mentioned here:
https://en.wikipedia.org/wiki/Comparison_of_data_serialization_formats
@neunhoef: Please validate below template and fill in the gaps (IDL/API/zero-copy)
And the note regarding references, to be added below the table and the other notes:
The text was updated successfully, but these errors were encountered: