Recent changes to Home

Home modified by Bjorn Reese

Bjorn Reese — Mon, 23 Feb 2015 13:55:40 -0000

--- v11
+++ v12
@@ -5,6 +5,7 @@
 * [JSON](http://json.org/)
 * [MessagePack](http://msgpack.org/)
 * [Transenc](http://transenc.sourceforge.net/)
+* [UBJSON](http://ubjson.org/) (draft 9)

 Supports two types of serialization: full parsing results in a [Document Object Model](http://en.wikipedia.org/wiki/Document_Object_Model), and pull parsing is useful for streaming input.

Home modified by Bjorn Reese

Bjorn Reese — Thu, 08 May 2014 07:23:33 -0000

--- v10
+++ v11
@@ -6,9 +6,28 @@
 * [MessagePack](http://msgpack.org/)
 * [Transenc](http://transenc.sourceforge.net/)

-Supports two types of serialization: pull parsing is useful for streaming input, and full parsing that results in a [Document Object Model](http://en.wikipedia.org/wiki/Document_Object_Model).
+Supports two types of serialization: full parsing results in a [Document Object Model](http://en.wikipedia.org/wiki/Document_Object_Model), and pull parsing is useful for streaming input.

 Compatible with Boost.Serialization.
+
+### Full Parsing ###
+
+The full parser transforms the entire input into a data structure. This is done via an input archive (called iarchive.) You can either use a generic tree data structure, such as [dynamic-cpp](http://dynamic-cpp.googlecode.com/), as the Document Object Model, or you can parse the input directly into your own data structures or the standard containers in C++.
+
+    :::C++
+    iarchive input(buffer.data(), buffer.data() + buffer.size());
+    dynamic::var result;
+    input >> result;
+

+
+Formatting a full data struture is done with an output archive (called oarchive.)
+
+    :::C++
+    dynamic::var data;
+    // Insert some values into data
+    std::ostringstream result;
+    stream_oarchive output(result)
+    output << data;

 ### Pull Parsing ###

@@ -41,25 +60,6 @@
     std::cout << output.str() << std::endl;
 


-### Full Parsing ###
-
-The full parser transforms the entire input into a data structure. This is done via an input archive (called iarchive.) You can either use a generic tree data structure, such as [dynamic-cpp](http://dynamic-cpp.googlecode.com/), as the Document Object Model, or you can parse the input directly into your own data structures or the standard containers in C++.
-
-    :::C++
-    iarchive input(buffer.data(), buffer.data() + buffer.size());
-    dynamic::var result;
-    input >> result;
-

-
-Formatting a full data struture is done with an output archive (called oarchive.)
-
-    :::C++
-    dynamic::var data;
-    // Insert some values into data
-    std::ostringstream result;
-    stream_oarchive output(result)
-    output << data;
-
 ## Depedencies ##

 Depends on Boost.Serialization. Test suites depends on Boost.Test.

Home modified by Bjorn Reese

Bjorn Reese — Wed, 09 Apr 2014 16:12:07 -0000

--- v9
+++ v10
@@ -12,28 +12,33 @@

 ### Pull Parsing ###

-The pull parser (called reader) is based on the [Iterator design pattern](http://en.wikipedia.org/wiki/Iterator_pattern), where the input is interpreted piece by piece. The API is something like this:
+The pull parser (called reader) is based on the [Iterator design pattern](http://en.wikipedia.org/wiki/Iterator_pattern), where the input is interpreted piece by piece. A simple example is:

     :::C++
-    class reader
-    {
-    public:
-        bool next(); // Advances to the next token
-        token type(); // Returns the current token
-        int get_bool() const; // Returns current value as boolean
-        // ... and so on for other types
-    };
+    std::string buffer = "[42, 43]";
+    json::reader reader(buffer.data(), buffer.data() + buffer.size());
+    assert(reader.type() == token::token_array_begin);
+    reader.next();
+    std::cout << reader.get_integer() << std::endl;
+    reader.next();
+    std::cout << reader.get_integer() << std::endl;
+    reader.next();
+    assert(reader.type() == token::token_array_end);
+    reader.next();
+    assert(reader.type() == token::token_eof);
 


-Pull parsers are often paired with push formatters (called writer), which will create the output stream piece by piece:
+Pull parsers are often paired with push formatters (called writer), which will create the output stream piece by piece. This example shows how to recreate the parsed buffer from the previous example:

     :::C++
-    class writer
-    {
-    public:
-        void write(bool); // Ouputs a boolean
-        // ... and so on for other types
-    };
+    std::ostringstream output;
+    output_stream buffer(output);
+    json::writer writer(buffer);
+    writer.write_array_begin();
+    writer.write(42);
+    writer.write(43);
+    writer.write_array_end();
+    std::cout << output.str() << std::endl;
 


 ### Full Parsing ###

Home modified by Bjorn Reese

Bjorn Reese — Thu, 27 Mar 2014 21:29:17 -0000

--- v8
+++ v9
@@ -1,9 +1,60 @@
-C++ pull parsing and serialization for various encoding formats:
+# Protocol Serialization #

+C++ serialization of various encoding formats:
+
+* [JSON](http://json.org/)
+* [MessagePack](http://msgpack.org/)
 * [Transenc](http://transenc.sourceforge.net/)
-* [JSON](http://json.org/)

-The following encoding formats are under development:
+Supports two types of serialization: pull parsing is useful for streaming input, and full parsing that results in a [Document Object Model](http://en.wikipedia.org/wiki/Document_Object_Model).

-* [MessagePack](http://msgpack.org/)
-* [Univeral Binary JSON](http://ubjson.org/)
+Compatible with Boost.Serialization.
+
+### Pull Parsing ###
+
+The pull parser (called reader) is based on the [Iterator design pattern](http://en.wikipedia.org/wiki/Iterator_pattern), where the input is interpreted piece by piece. The API is something like this:
+
+    :::C++
+    class reader
+    {
+    public:
+        bool next(); // Advances to the next token
+        token type(); // Returns the current token
+        int get_bool() const; // Returns current value as boolean
+        // ... and so on for other types
+    };
+

+
+Pull parsers are often paired with push formatters (called writer), which will create the output stream piece by piece:
+
+    :::C++
+    class writer
+    {
+    public:
+        void write(bool); // Ouputs a boolean
+        // ... and so on for other types
+    };
+

+
+### Full Parsing ###
+
+The full parser transforms the entire input into a data structure. This is done via an input archive (called iarchive.) You can either use a generic tree data structure, such as [dynamic-cpp](http://dynamic-cpp.googlecode.com/), as the Document Object Model, or you can parse the input directly into your own data structures or the standard containers in C++.
+
+    :::C++
+    iarchive input(buffer.data(), buffer.data() + buffer.size());
+    dynamic::var result;
+    input >> result;
+

+
+Formatting a full data struture is done with an output archive (called oarchive.)
+
+    :::C++
+    dynamic::var data;
+    // Insert some values into data
+    std::ostringstream result;
+    stream_oarchive output(result)
+    output << data;
+
+## Depedencies ##
+
+Depends on Boost.Serialization. Test suites depends on Boost.Test.

Home modified by Bjorn Reese

Bjorn Reese — Fri, 07 Mar 2014 09:03:11 -0000

--- v7
+++ v8
@@ -1,4 +1,4 @@
-C++ serialization for various encoding formats:
+C++ pull parsing and serialization for various encoding formats:

 * [Transenc](http://transenc.sourceforge.net/)
 * [JSON](http://json.org/)

Home modified by Bjorn Reese

Bjorn Reese — Fri, 31 Jan 2014 13:58:18 -0000

--- v6
+++ v7
@@ -1,9 +1,9 @@
 C++ serialization for various encoding formats:

 * [Transenc](http://transenc.sourceforge.net/)
+* [JSON](http://json.org/)

 The following encoding formats are under development:

-* [JSON](http://json.org/)
 * [MessagePack](http://msgpack.org/)
 * [Univeral Binary JSON](http://ubjson.org/)

Home modified by Bjorn Reese

Bjorn Reese — Sun, 04 Aug 2013 13:21:56 -0000

--- v5
+++ v6
@@ -1,6 +1,9 @@
 C++ serialization for various encoding formats:

-* [JSON](http://json.org/) (under development)
-* [MessagePack](http://msgpack.org/) (under development)
-* [Transenc](http://transenc.sourceforge.net/) (under development)
-* [Univeral Binary JSON](http://ubjson.org/) (under development)
+* [Transenc](http://transenc.sourceforge.net/)
+
+The following encoding formats are under development:
+
+* [JSON](http://json.org/)
+* [MessagePack](http://msgpack.org/)
+* [Univeral Binary JSON](http://ubjson.org/)

Home modified by Bjorn Reese

Bjorn Reese — Tue, 02 Apr 2013 14:04:45 -0000

--- v4
+++ v5
@@ -1,4 +1,4 @@
-C++ encoder/decoder for various binary formats:
+C++ serialization for various encoding formats:

 * [JSON](http://json.org/) (under development)
 * [MessagePack](http://msgpack.org/) (under development)

Home modified by Bjorn Reese

Bjorn Reese — Tue, 02 Apr 2013 14:03:52 -0000

--- v3
+++ v4
@@ -1,5 +1,6 @@
 C++ encoder/decoder for various binary formats:

+* [JSON](http://json.org/) (under development)
 * [MessagePack](http://msgpack.org/) (under development)
 * [Transenc](http://transenc.sourceforge.net/) (under development)
 * [Univeral Binary JSON](http://ubjson.org/) (under development)

WikiPage Home modified by Bjorn Reese

Bjorn Reese — Wed, 20 Mar 2013 11:08:45 -0000

--- v2
+++ v3
@@ -1,4 +1,5 @@
 C++ encoder/decoder for various binary formats:

-* [MessagePack](http://msgpack.org/)
-* [Univeral Binary JSON](http://ubjson.org/)
+* [MessagePack](http://msgpack.org/) (under development)
+* [Transenc](http://transenc.sourceforge.net/) (under development)
+* [Univeral Binary JSON](http://ubjson.org/) (under development)