Call the extra_watch_callback on a different thread than the dispatcher

Otherwise, a call to e.g. Xs.read will deadlock if you try to do it
from the callback.

Signed-off-by: Jon Ludlam <jonathan.ludlam@eu.citrix.com>
Add a test to check that reads work in a watch callback

Signed-off-by: Jon Ludlam <jonathan.ludlam@eu.citrix.com>
Merge pull request #8 from jonludlam/watch-callbacks-on-separate-thread

Watch callbacks on separate thread
Fix build cycle between xenstore and xenstore_transport by removing
the client_unix test.

This whole test should be moved to a different repository, leaving
this one as the `portable core`.

Signed-off-by: Anil Madhavapeddy <anil@recoil.org>
Merge pull request #9 from avsm/fix-build-cycle

Fix build cycle between xenstore and xenstore_transport by removing
The watch callback thread wasn't dealing with exceptions

This commit fixes this and also removes logging to stderr
in favour of a logging callback.

Signed-off-by: Jon Ludlam <jonathan.ludlam@eu.citrix.com>
Merge pull request #10 from jonludlam/fix-watch-callback-thread

The watch callback thread wasn't dealing with exceptions
make doc
[doc] Xs_client, Xs_client_unix: cosmetics
Updated doc title for Xs_client, Xs_client_unix
Improved doc for module Xs_protocol
Rewritten module Xs_handle to be more functional style, with better interface and documentation
Renamed with_xs/with_xst -> immediate/transaction (like in Mirage)
Make the xs_client_unix look more like the lwt one, renamed xs_client to xs_client_lwt for more consistency.
Updated CHANGES.