Merge pull request #111 from ably/fix-rsl1g1b

RSL1g1b: Ably does assign clientId in messages

textile/features.textile

@@ -176,7 +176,7 @@ h3(#rest-channel). Channel
 ** @(RSL1g)@ Identified clients with a @clientId@ (as a result of either an explicitly configured @clientId@ in @ClientOptions@, or implicitly through Token Auth):
 *** @(RSL1g1)@ When publishing a @Message@ with the @clientId@ attribute set to @null@:
 **** @(RSL1g1a)@ It is unnecessary for the client to set the @clientId@ of the @Message@ before publishing
-**** @(RSL1g1b)@ Ably will not assign a @clientId@ upon receiving the @Message@. A test should assert via the history API that the @clientId@ value is @null@ for the @Message@ when received
+**** @(RSL1g1b)@ Ably will assign the identified @clientId@ upon receiving the @Message@. A test should assert via the history API that the @clientId@ value is the identified @clientId@ for the @Message@ when received
 *** @(RSL1g2)@ When publishing a @Message@ with the @clientId@ attribute value set to the identified client's @clientId@, Ably will accept the message and publish it. A test should assert that the @clientId@ value is populated for the @Message@ when received
 *** @(RSL1g3)@ When publishing a @Message@ with a different @clientId@ attribute value to the identified client's @clientId@, the client library should reject the message, and indicate an error. The connection and channel remain available for further operations
 *** @(RSL1g4)@ When publishing a message with an explicit @clientId@ that is incompatible with the identified client's @clientId@ (either inferred or explicitly configured in the token or @ClientOptions@), the library will reject the message immediately and indicate an error