Link Details

The need for a format to serialize data is as old as networking itself. In the early days of data processing, the problem was attacked by use of binary protocols — that is, protocols with data that was not human readable. These were frequently custom-defined on an ad hoc basis. The sender and receiver had to agree on where fields were located and what they contained in order to exchange data. These schemes eventually gave way, in part, to emerging standards such as ASN.1

Posted by Jeremy Morgan  |   Submitted: Mar 30 2013 / 10:25

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.


User 368023 avatar

yakkoh replied ago:

The next serialize data format should have the following attributes: (1) readable AND writable by human programmers with a standard text editor (2) support for datatype like date and time, floating numbers, currency, binary data (3) include statement (4) support for names, like customer_name, birth_date, current_location (5) make a difference between a hash structure and an array structure (6) a clear mapping between the programming language vs the datatypes and data structures: if the language doesn't exist then invent it. More or less JSON but with new features.

Reply 0 votes

Recommended Links

Upvoters (2)

Downvoters (0)

    Written by: Ryan Knight
    Featured Refcardz: Top Refcardz:
    1. Apache Hadoop
    2. Play
    3. Akka
    4. Debugging JavaScript
    5. Design Patterns
    1. Apache Hadoop
    2. REST
    3. Java
    4. Git
    5. Java Performance
    Connect with DZone