Skip to content

Commit 3824174

Browse files
committed
Added missing spec for calculating message size using given name and clientId
1 parent 59b42e9 commit 3824174

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

textile/features.textile

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1454,6 +1454,8 @@ h4. Message
14541454
** @(TM6b)@ The size of an @Object@ or @Array@ @data@ property is its string length after being JSON-stringified
14551455
** @(TM6c)@ The size of a @binary@ @data@ property is its size in bytes (of the actual binary, not the base64 representation, regardless of whether the binary protocol is in use)
14561456
** @(TM6f)@ The size of a @string@ @data@ property is its length
1457+
** @(TM6g)@ The size of a @string@ @name@ property is its length
1458+
** @(TM6h)@ The size of a @string@ @clientId@ property is its length
14571459
** @(TM6d)@ The size of the @extras@ property is the string length of its JSON representation
14581460
** @(TM6e)@ The size of a @null@ or omitted property is zero
14591461
* @(TM7)@ The SDK may expose a series of functions (static factory methods on a Message or otherwise, wherever is language idiomatic; for some languages this might just be types that can be used for type assertions, etc), that take a deserialized @JsonObject@, one of the aggregated summaries for a particular annotation type (that is, a value from the @TM2q@ @summary@ @Dict@), and outputs a strongly-typed summary entry, for ease of use by the end user (particularly in languages where manipulating plain objects is difficult).

0 commit comments

Comments
 (0)