Ricky Sharp wrote:
As for the transport, I would highly recommend UTF-8 as no
byteswapping is needed. For most Latin-based data, the number of
bytes taken up in UTF-8 will be less than what is used by UTF-16.
For Japanese (and many other languages), the number of bytes of
UTF-8 will be more than UTF-16. Just wanted to point that out in
case you have insanely strict bandwidth requirements.
Depending on what the server and client are using as the transport
protocol, it may support a compressed encoding. For example, HTTP
1.1 has a gzip option for content encoding (also compress and
deflate, but in my experience gzip is more often seen). See sec. 3.5
Content Codings of RCC2616.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html
In general, a client states its supported encodings and the server
chooses, or the two participants negotiate. Again, this depends on
what the transport protocol is: not all of them support compression.
-- GG
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
