What is the practical limit for endpoint info size in bytes? #3152
-
For example, see: ConnectionsClient#startAdvertising The method accepts endpoint info as a byte array that I would like to use to share some basic info about the client which is advertising. Similar endpointInfo byte array arguments are used in a few other API signatures as well. From some basic digging I have found:
That being said, it appears that nearby connections includes some basic metadata of its own, which I assume contributes to these limits... And the API doesn't seem to guarantee a specific technology for each connection strategy, so it's hard to know which limitations might apply. Is there a recommended practical limit to these for nearby connections? I imagine nearby connections might have some underlying tricks to bypass this limitation, but the API documentation doesn't offer any guidance, so I figured I'd check. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
131 bytes is the cap |
Beta Was this translation helpful? Give feedback.
-
A few follow-up questions -- is this a generally applicable limit for And is this limit subject to decrease? Or is this expected to be pretty stable? |
Beta Was this translation helpful? Give feedback.
131 bytes is the cap