Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
C
capnproto
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
capnproto
Commits
af03c043
Commit
af03c043
authored
May 01, 2013
by
Kenton Varda
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add note about ID collisions.
parent
dd299bd6
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
0 deletions
+5
-0
language.md
doc/language.md
+5
-0
No files found.
doc/language.md
View file @
af03c043
...
@@ -407,6 +407,11 @@ but this would have some important disadvantages in the context of Cap'n Proto:
...
@@ -407,6 +407,11 @@ but this would have some important disadvantages in the context of Cap'n Proto:
distributed system with many different binaries using different versions of protocols.
distributed system with many different binaries using different versions of protocols.
*
Fully-qualified type names may be large and waste space when transmitted on the wire.
*
Fully-qualified type names may be large and waste space when transmitted on the wire.
Note that IDs are 64-bit (actually, 63-bit, as the first bit is always 1). Random collisions
are possible, but unlikely -- there would have to be on the order of a billion types before this
becomes a real concern. Collisions from misuse (e.g. copying an example without changing the ID)
are much more likely.
## Advanced Topics
## Advanced Topics
### Dynamically-typed Fields
### Dynamically-typed Fields
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment