- The ARX file format should be saved in network byte order.

- What about assignment operators for Marker, BufferReader and BufferWriter?

- Is it feasible to make ARX archives work like NTFS volumes. This way,
  modifying the ARX standard would be much easier and new item properties could
  be realized without changing the binary format of an ARX archive.

- Handle HTTP1.1 return codes in Test5.

- Consider making archives only filesystem which can be mounted on different
  points of a more global structure.

- Since there is a need for asynchronous actions for fetchers, it is important
  to add the logistic background to handle asynchronous, concurrent events.
  This is done via a global class Arxx::Poller. Arxx::Poller has a standard
  instantiation that is used whenever no other instance is assigned to an
  asynchronous process. Assigning other Pollers could be done on various levels
  but is omitted for now. Arxx::Poller needs a function
  Arxx::Poller::bHasTasks() that returns true if Arxx::Poller::vPoll() should
  be called to give asynchronous tasks the chance to act.

- Arxx::Data should be made safe against wrong values in DecompressedLength.
  If you decompress a buffer currently we rely on DecompressedLength being
  valid, but we should not. Also a maximum size of the decompression buffer
  should be put into place to prevent potential 4Gigs of allocated buffer.

- Investigate whether making Arxx::Structure a base class of Arxx::Item poses
  any problems.

- Add a Arxx internal extension system for data channels. Packages can install
  .so files into ${prefix}/lib/libarxx/ and paths in the ARXX_DATAFETCHERS_PATH
  environment variable and ARXX can list, load, unload and
  load-unload-on-demand those extension, registering their data channels at the
  Arxx::DataRepository. It should be possible to load all available plugins with
  a single call at application setup time and thereafter have full access to the
  data channels. What is to be done about multiple data channels for the same
  URI?

- Extensions can be configured via a propertymap which can be set for all
  extensions at once and individually. Extensions propose properties, types and
  default values. Extensions have to supply unique identifiers and version
  numbers, external of the property map. The property maps should be considered
  extension-input only.

- There is still that URI relativity tree to build up in an ARX archive file.
  The build has to be performed on save the reconstruction of absolute URIs on
  load. No delayed evaluation here.

- It has to be made possible to load libraries from remote systems using the
  DataChannels. This may be done implementing the library load routine using
  Arxx::Data.

- There is a definite need for load and save interrupts. You pass a pointer to
  a LoadManager to the Arxx::Library::bLoad function and bLoad will set up
  everything ready to go but then return to the calling context. From now on
  your LoadManager has to be told to initiate the next part of the load
  process. Depending on the interrupt flags you set on the LoadManager it can
  be configured to stop every so often so that you update your UI or initiate
  additional calculations.
