Devel

Valgrind tests on both client side and server side passed, no regressions regarding memory access found.

It's worthwhile to note that the content of the global DOM tree of the oBIX sever comes from below possible sources:
1. static configuration files or data files (history index files);
2. signUp by client (through signUp request);
3. inserted by client (through a normal write request);
4. signOff by client (not implemented yet).

To start with, there is no parser dictionary manipulated on the server side. Optimisation in this regard may be done in the near future once we have figured out how to maintain the consistency of a parser dictionary especially in a multi-thread environment.