Changes between Version 11 and Version 12 of ariba_0_9


Ignore:
Timestamp:
Jun 21, 2013, 11:58:52 AM (11 years ago)
Author:
hock@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ariba_0_9

    v11 v12  
    3939To get to code, please check out the latest trunk version from our svn: [https://i72projekte.tm.uka.de/SpoVNet-KA/entwicklung/ariba/trunk Ariba-SVN]
    4040
    41 === Configuration format ===
     41=== ''' Configuration format ''' ===
    4242Ariba 0.9.x uses a new configuration format, based in boost::property_tree. Hence you can use the JSON format to store ariba configs. Other formats (e.g. XML) are supported, too. Please refor to the documentation: [http://www.boost.org/doc/libs/1_46_1/doc/html/property_tree.html Boost.PropertyTree]
    4343
    … …  
    7474Note that all ariba related config is stored in a field named `ariba`. The same JSON file can be used to store application specific config data as well.
    7575
    76 === Ping-pong example ===
     76=== ''' Ping-pong example ''' ===
    7777The ping-pong code in the SVN trunk differs from the detailed explanation in the wiki. Especially the new config format (see above) and `Node::connect`, the new easy and clean interface to start-up ariba (see below) is used.
    7878
    … …  
    137137    - `ariba/Node.h`.
    138138
    139 === Message formats ===
     139=== ''' Message formats ''' ===
    140140
    141141The ping pong example still uses the old deprecated ariba::message messages with the ariba built-in serialization. For future applications please use the new reboost::message_t messages. Data is stored in high efficient zero-copy buffers of type reboost::shared_buffer_t. These buffers hold plain data, so you have to serialize the data "on your own".