[PATCH docs] Clarify the wire format array specification

[Bill Spitzak]

I think it is confusing to call this an "array", rather than perhaps a 
"block" or something.

When I read the documentation I thought the array consisted of N pieces 
of data in wire format, not N bytes.

Micah Nordland wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Addition to the wire format specification array type definition to say
> that array contents are defined by whatever is using the array.
> 
> diff --git a/doc/publican/sources/Protocol.xml
> b/doc/publican/sources/Protocol.xml
> index b79b6be..039d875 100644
> - --- a/doc/publican/sources/Protocol.xml
> +++ b/doc/publican/sources/Protocol.xml
> @@ -148,6 +148,8 @@
>             <para>
>               Starts with 32-bit array size in bytes, followed by the
> array
>               contents verbatim, and finally padding to a 32-bit boundary.
> +          The type of the items in the array are defined by the request
> +          or event using the array.
>             </para>
>           </listitem>
>         </varlistentry>
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQEcBAEBAgAGBQJSRf9bAAoJEPBh3Rt3H/83U/EH/2AJY7atz6iPM2mhIC6zT4eV
> yuNGtb5+YOWlaa0VaF9ljeLaYdy09F8J5WUvLfLzKtfBKTOqDDNdo/wrfBDqw7im
> K/FYFnvp6ICwWrkrP2f38zKloWuXE5BLq8dqKwkDt6XbNnBB5f8eQrTxFRf1TJb3
> uZ+U2Lgj2z+y320hupOsUkIk4jvNrtVQ+kiN6DZtpxV80qzmx7ZkeV1RPN+rIr1F
> M/cct2kIcPeQWPFdGsIA2GzewB8j4vgD5McAIL7U/HPdaBsObQDom7dAq60p90Re
> wDrELKjqQq4sZJY3bxZtxZREQpXN4x9kxapWM5cTGFBDIZuEpC4FWYt+9Dex18U=
> =IqQM
> -----END PGP SIGNATURE-----
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel