Loading ...
Sorry, an error occurred while loading the content.

Re: [json] Re: JSON representation of common types

Expand Messages
  • Matt
    Out of band data for creating types in other languages which don t cleanly/easily support raw javascript types should be done as optional data, which can still
    Message 1 of 19 , Aug 8, 2006
    • 0 Attachment
      Out of band data for creating types in other languages which don't
      cleanly/easily support raw javascript types should be done as optional
      data, which can still be encoded as json.

      It should be easy enough to take your objects before json encoding,
      and run them through a function to turn them into wrapper objects, the
      additional data you need being stored in properties, without polluting
      json or json-rpc directly.

      Assuming you know that the consumer of the data needs these additional
      suggestions as to type election, otherwise as Andy said that `burden`
      should be on the decoder to figure it out.


      --
      Matthew P. C. Morley
      MPCM Technologies Inc.
    Your message has been successfully submitted and would be delivered to recipients shortly.