19/Oct/2002: Creating and renaming objects check to make sure the ID does
not already exist.

5/Jan/2003: Deletion of non-empty tree items is now possible with a single
request.

8/Feb/2003: A major new feature is underway - actually the 4th part of the
CRK suite, Xuru, which the computational scheduler, allowing one or more
computers to participate in a "compute farm". The idea is based on adding
new functionality to Xortoth to keep track of computations which are
requested ahead of time, and will be conducted at the next available
opportunity. The interface is provided as a part of Xykron, some
additional streamlining features will be added to Xentark, and Xuru itself
will be a daemon which runs on each computer designated as part of the
farm. This feature will probably remain primarily internal for some time,
since it requires that all the CRK components are operational, but the
software will be made available from the outset. NOTE: If anybody is
actually using Xortoth at the moment, there is an additional MySQL table
that is needed, and the PHP pages have been diversified somewhat.

22/Feb/2003: Completion of the new Xortoth features required to support
Xuru.

23/Apr/2003: Improved configurability for Xortoth: now a file 'datasources'
is read to ascertain a list of MySQL databases, and their appropriate
connection parameters. The webservice page, FatClient.php, takes an
optional form parameter, as '?db=<database>' which may be used to indicate
which database is to be used for the connection. If omitted, the first
valid line in the 'datasources' file will be used.<BR>&nbsp;&nbsp;Further
improvements to Xortoth's installability will ensue.

26/Apr/2003: Xortoth has been rewired to include security, and the other
CRK packages updated accordingly to make use of it. There is a new
database table, Perms, which manages users and groups. Presently security
is only implemented as far as gaining access to being able to use Xortoth,
or not. Actual permission granularity is next, and will be Unix-like
(owner/group/all).<BR>&nbsp;&nbsp;On a general note, Xortoth security will
not likely be "hardened" in the immediate future. Although there are some
common sense precautions, like using MD5 hashes through the webservice
interface and for passing passwords as parameters, there are still plenty
of ways a hacker could take advantage of a naive admin.

3/May/2003: User-login security and user-management implementation is
complete. Also, fields have been added to the Tree table to facilitate
Unix-like permissions on parts of the hierarchy; these are, however, not
yet used.
