This page presents a very simple client to access a server that implements the file system we developed in Slice for a Simple File System. The C++ code shown here hardly differs from the code you would write for an ordinary C++ program. This is one of the biggest advantages of using Ice: accessing a remote object is as easy as accessing an ordinary, local C++ object. This allows you to put your effort where you should, namely, into developing your application logic instead of having to struggle with arcane networking APIs. This is true for the server side as well, meaning that you can develop distributed applications easily and efficiently.
We now have seen enough of the client-side C++ mapping to develop a complete client to access our remote file system. For reference, here is the Slice definition once more:
module Filesystem { interface Node { idempotent string name(); } exception GenericError { string reason; } sequence<string> Lines; interface File extends Node { idempotent Lines read(); idempotent void write(Lines text) throws GenericError; } sequence<Node*> NodeSeq; interface Directory extends Node { idempotent NodeSeq list(); } } |
To exercise the file system, the client does a recursive listing of the file system, starting at the root directory. For each node in the file system, the client shows the name of the node and whether that node is a file or directory. If the node is a file, the client retrieves the contents of the file and prints them.
The body of the client code looks as follows:
#include <Ice/Ice.h> #include <Filesystem.h> #include <iostream> #include <iterator> using namespace std; using namespace Filesystem; static void listRecursive(const DirectoryPrx& dir, int depth = 0) { // ... } int main(int argc, char* argv[]) { int status = 0; try { // Create a communicator // Ice::CommunicatorHolder ich(argc, argv); // Create a proxy for the root directory // Ice::ObjectPrx base = ich->stringToProxy("RootDir:default -p 10000"); if(!base) { throw "Could not create proxy"; } // Down-cast the proxy to a Directory proxy // DirectoryPrx rootDir = DirectoryPrx::checkedCast(base); if(!rootDir) { throw "Invalid proxy"; } // Recursively list the contents of the root directory // cout << "Contents of root directory:" << endl; listRecursive(rootDir); } catch(const Ice::Exception& ex) { cerr << ex << endl; status = 1; } catch (const char* msg) { cerr << msg << endl; status = 1; } return status; } |
Ice/Ice.h
:Filesystem.h
:Filesystem.ice
.iostream
:iostream
library to produce its output.iterator
:listRecursive
uses an STL iterator.using
declarations for the std
and Filesystem
namespaces.main
follows what we saw in Hello World Application. After initializing the run time, the client creates a proxy to the root directory of the file system. For this example, we assume that the server runs on the local host and listens using the default protocol (TCP/IP) at port 10000. The object identity of the root directory is known to be RootDir
.DirectoryPrx
and passes that proxy to listRecursive
, which prints the contents of the file system.Most of the work happens in listRecursive
:
// Recursively print the contents of directory "dir" in // tree fashion. For files, show the contents of each file. // The "depth" parameter is the current nesting level // (for indentation). static void listRecursive(const DirectoryPrx& dir, int depth = 0) { string indent(++depth, '\t'); NodeSeq contents = dir->list(); for(NodeSeq::const_iterator i = contents.begin(); i != contents.end(); ++i) { DirectoryPrx dir = DirectoryPrx::checkedCast(*i); FilePrx file = FilePrx::uncheckedCast(*i); cout << indent << (*i)->name() << (dir ? " (directory):" : " (file):") << endl; if(dir) { listRecursive(dir, depth); } else { Lines text = file->read(); for(Lines::const_iterator j = text.begin(); j != text.end(); ++j) { cout << indent << "\t" << *j << endl; } } } } |
The function is passed a proxy to a directory to list, and an indent level. (The indent level increments with each recursive call and allows the code to print the name of each node at an indent level that corresponds to the depth of the tree at that node.) listRecursive
calls the list operation on the directory and iterates over the returned sequence of nodes:
checkedCast
to narrow the Node
proxy to a Directory
proxy, as well as an uncheckedCast
to narrow the Node
proxy to a File
proxy. Exactly one of those casts will succeed, so there is no need to call checkedCast
twice: if the Node
is-a Directory
, the code uses the DirectoryPrx
returned by the checkedCast
; if the checkedCast
fails, we know that the Node
is-a File
and, therefore, an uncheckedCast
is sufficient to get a FilePrx
.uncheckedCast
instead of a checkedCast
because an uncheckedCast
does not incur any network traffic."(directory)"
or "(file)"
following the name.read
operation on the file to retrieve the file contents and then iterates over the returned sequence of lines, printing each line.Assume that we have a small file system consisting of two files and a directory as follows:
A small file system.
The output produced by the client for this file system is:
Contents of root directory: README (file): This file system contains a collection of poetry. Coleridge (directory): Kubla_Khan (file): In Xanadu did Kubla Khan A stately pleasure-dome decree: Where Alph, the sacred river, ran Through caverns measureless to man Down to a sunless sea. |
Note that, so far, our client (and server) are not very sophisticated:
We will see how to address these shortcomings in our discussions of IceGrid and object life cycle.