[Home]	[About]
[Screenshots]	[Download]
[News]	[Community]
[Documentation]	[Manual]
[Bugs & Requests]	[Wiki]

/home/tetron/hack/vos/apps/tutorials/vostut4.cc

Go to the documentation of this file.

/* Fourth VOS tutorial.  Linking Vobjects together.

   This tutorial covers:
   - Inserting, replacing and removing Vobjects as children of other
   Vobjects
   - Linking local and remote Vobjects
   - Finding specific a child by name
   - Vobject paths
   - Listing a Vobject's children
   - Listing a Vobject's parents

   This file (vostut4.cc) is released into the public domain.  No
   restrictions are placed on its use, distribution or inclusion into
   other works.
*/

#include <vos/vos/vos.hh>

using namespace VUtil;
using namespace VOS;

#ifdef WIN32
#define sleep _sleep
#endif

void listChildren(Vobject* vobject);
void listParents(Vobject* vobject);

// The server from tutorial 3 ("vostut3server") should be run before
// running this tutorial.

int main(int argc, char** argv)
{
    std::cout << "VOS Tutorial 4\n\n";

    Site localsite;
    localsite.addSiteExtension(new LocalVipSiteExtension());
    localsite.setDefaultPolicy("core:accept-all");

    /* We saw in the previous tutorial how one Vobject can access
       another.  We now look at how Vobjects may be linked together to
       create network-accessable data structures.  In this tutorial,
       we demonstrate how one might build a data structure describing
       a sphere with VOS.

       A Vobject may consist of a number of incoming "parent" links
       and outgoing "child" links.  The terms parent and child come
       from common computer science usage for describing hierarchical
       structures.  At the top level is the local site, which is a
       parent to all Vobjects it hosts (and therefore has each Vobject
       as a child).  When a Vobject is created, it is automatically
       made a child of its site.
    */

    // Create some objects to play with.
    vRef<Vobject> sphere = localsite.createVobjectA("sphere");
    vRef<Vobject> tertius = localsite.createVobjectA("tertius");
    vRef<Vobject> quartus = localsite.createVobjectA("quartus");
    vRef<Vobject> quintus = localsite.createVobjectA("quintus");
    vRef<Vobject> sextus = localsite.createVobjectA("sextus");
    vRef<Vobject> septimus = localsite.createVobjectA("septimus");

    // Permit remote sites to access these objects:
    sphere->setDefaultPolicy("core:accept-all");
    tertius->setDefaultPolicy("core:accept-all");
    quartus->setDefaultPolicy("core:accept-all");
    quintus->setDefaultPolicy("core:accept-all");
    sextus->setDefaultPolicy("core:accept-all");
    septimus->setDefaultPolicy("core:accept-all");

    listChildren(&localsite);
    std::cout << "\n";

    /* Each Vobject stores a list other Vobjects it links to. This is
       called the child list.  It is an ordered, associative list,
       where each position in the list consists of a string called the
       "contextual name" and a link to the Vobject it points to.

       Initially, the Vobject "sphere" does not have any children.
       The insertChild() method is used to add children.  The first
       parameter tells where in the list to insert the child, with the
       value "-1" used to append to the end of the child list.  The
       link is named "position", so in our example the the linked-to
       child vobject (tertius) describes the position of its parent
       (the sphere).
    */
    std::cout << "Appending tertius as \"position\"\n";
    sphere->insertChild(-1, "position", tertius);

    /* For the moment, don't worry about how the value of position
        will be stored in the tertius Vobject. This is discussed in a
        later tutorial.  For this tutorial we are concentrating on the
        abstract structure.
     */

    /* Print out the children of the sphere and the parents of
       tertius.  Since tertius has been added as a child to sphere,
       sphere is now listed as a parent of tertius.
    */
    listChildren(sphere);
    listParents(tertius);
    std::cout << "\n";


    /* Now we add a few more vobjects to the sphere.  As demonstrated
       here, the child list can have more than one link to the same
       Vobject and you can have multiple entries with the same
       contextual name.
    */
    std::cout << "Appending quartus as \"orientation\"\n";
    sphere->insertChild(-1, "orientation", quartus);

    std::cout << "Appending quintus as \"radius\"\n";
    sphere->insertChild(-1, "radius", quintus);

    std::cout << "Appending quartus as \"position\"\n";
    sphere->insertChild(-1, "position", quartus);

    listChildren(sphere);
    listParents(quartus);
    std::cout << "\n";


    /* Of course we can insert a new item anywhere. We'll add the
       Vobject "sextus" describing the color of our sphere so that it
       occupies position 2.  This shifts the rest of the list (from
       position 2 to the end) up one position to make room for the
       newly inserted child.  Note: position 0 inserts a child at the
       beginning of the list.
    */
    std::cout << "Inserting sextus as \"color\" into position 2\n";
    sphere->insertChild(2, "color", sextus);

    listChildren(sphere);
    std::cout << "\n";


    /* Oops!  We have two children named "position"!  The sphere can't
       very well be in two places at once, can it?  The setChild()
       method allows us to replace a child at one position with
       another, which is much more efficient than removing the old
       vobject and inserting the new one.  Here we replace the second
       "position" child (at list position 4 now) with a
       different object that will store our sphere's mass.
    */
    std::cout << "Replacing quartus in position 4 with septimus as \"mass\"\n";
    sphere->setChild(4, "mass", septimus);

    listChildren(sphere);
    std::cout << "\n";

    /* It's also sort of silly for a sphere to have an orientation,
       seeing as how it is perfectly round.  Let's remove the child
       storing the orientation.  The removeChild() method removes the
       list item at the given position and move everything above it
       down a notch to fill in the gap.
     */
    std::cout << "Removing quintus (\"orientation\") from position 1\n";
    sphere->removeChild(sphere->findChild(1));

    listChildren(sphere);
    std::cout << "\n";


    /*  Some detail specifying a position in a child list: positive
        positions are counted from the beginning and negative
        positions are counted from the end.  The start of the list is
        always 0 and the end of the list is always -1.  This means
        that positions of -2 (second-to-last position), -3, -10 and so
        on are perfectly legal (provided the list is at least of that
        length).
     */
    std::cout << "Removing septimus (\"mass\") from the last position\n";
    sphere->removeChild(sphere->findChild(-1));

    listChildren(sphere);
    std::cout << "\n";

    try {
        /* What makes parent-child linking of Vobjects really
           interesting is the fact that you can freely mix local and
           remote Vobjects.  Here we acquire a remote object running
           on a different site and manipulate it exactly the same way
           as if it were local.
         */
        vRef<Vobject> primus = Vobject::findObjectFromRoot("vip://localhost:4231/primus");

        std::cout << "Adding local vobject septimus to remote vobject primus\n";
        primus->insertChild(-1, "septimus", septimus);

        listChildren(primus);
        listParents(septimus);
        std::cout << "\n";


        std::cout << "Adding remote vobject primus to local vobject quartus\n";
        quartus->insertChild(-1, "primus", primus);

        listChildren(quartus);
        listParents(primus);
        std::cout << "\n";
    } catch(std::runtime_error& e) {
        std::cerr << "An exception occured: " << e.what() << "\n";
    }

    /* Once we have created a VOS data structure, we want to be able
       to access it. One way is by iterating over the entire contents
       of the child list (which is demonstrated in the listChildren()
       function below).  The other is to use the findChild() and
       findObject() methods.

       The findChild() method returns the Vobject::ParentChildRelation
       structure describing the link with the given contextual name.
       If more than one link has the same contextual name, then the
       link with position closest to the beginning is returned. This
       simply consists of four fields, the parent, the child, and the
       position and contextual name in the parent's child list.
    */
    vRef<ParentChildRelation> pcr = sphere->findChild("color");
    std::cout << "Results of findChild():\n";
    std::cout << " Parent: " << pcr->getParent()->getURLstr() << "\n";
    std::cout << " Position: " << pcr->getPosition() << "\n";
    std::cout << " Contextual name: " << pcr->getContextualName() << "\n";
    std::cout << " Child: " << pcr->getChild()->getURLstr() << "\n";

    /* The findObject() method returns just the Vobject itself, but
       can take a path going through several Vobjects.  A Vobject path
       is a slash-separated list of contextual names to follow to find
       the Vobject.  It is intended to resemble a familiar file system
       path and works essentially the same way, although the notation
       ".." is not available.  While directories in a filesystem only
       have one parent directory, Vobjects usually have two or more
       parent Vobjects!
    */
    vRef<Vobject> color = localsite.findObject("sphere/color");

    listParents(color);

    /* One final method for accessing parent-child relationships:
       findParent() returns the parent-child relationship structure
       associated with a specific parent of this Vobject.
    */
    vRef<ParentChildRelation> pcr2 = color->findParent(sphere);
    std::cout << "Results of findParent():\n";
    std::cout << " Parent: " << pcr2->getParent()->getURLstr() << "\n";
    std::cout << " Position: " << pcr2->getPosition() << "\n";
    std::cout << " Contextual name: " << pcr2->getContextualName() << "\n";
    std::cout << " Child: " << pcr2->getChild()->getURLstr() << "\n";


    std::cout << "Going into runloop now.  Try connecting to " << localsite.getURLstr() << " using \"mesh\"\n";
    std::cout << "to inspect the current vobject structure.\n";

    while(true) sleep(1000);
}

void listChildren(Vobject* vobject)
{
    std::cout << "Children of " << vobject->getURL().getString() << ":\n";

    for(ChildListIterator childlist = vobject->getChildren();
        childlist.hasMore();
        childlist++)
    {
        vRef<ParentChildRelation> pcr = *childlist;
        std::cout << " #" << pcr->getPosition() << " " << pcr->getContextualName() << " -> "
                  << pcr->getChild()->getURLstr() << "\n";
    }
}

void listParents(Vobject* vobject)
{
    std::cout << "Parents of " << vobject->getURLstr() << ":\n";

    for(ParentSetIterator parentset = vobject->getParents();
        parentset.hasMore();
        parentset++)
    {
        vRef<ParentChildRelation> pcr = *parentset;
        std::cout << " " << pcr->getParent()->getURLstr() << " linked as #"
                  << pcr->getPosition() << " " << pcr->getContextualName() << "\n";
    }
}