Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Below are presented two encodings. The first is the simpler option and the second the more complex. The difference is that the second is optimized to avoid sending field names every time an object is serialized, which is done by caching metadata using type registration. We could potentially support both, but given that JSON is already the easy option, and since type registration is per-connection, caching classes on the client side should not be a big burden.   The recommendation is for Option 2. Option 1 below is included mostly to make the motivation for Option 2 clearer.

...