r2100: rework the dcerpc client side library so that it is async. We now

generate a separate *_send() async function for every RPC call, and
there is a single dcerpc_ndr_request_recv() call that processes the
receive side of any rpc call. The caller can use
dcerpc_event_context() to get a pointer to the event context for the
pipe so that events can be waited for asynchronously.

The only part that remains synchronous is the initial bind
calls. These could also be made async if necessary, although I suspect
most applications won't need them to be.

source/lib/events.c

@@ -403,7 +403,7 @@ void event_loop_once(struct event_context *ev)
 			   made readable and that should have removed
 			   the event, so this must be a bug. This is a
 			   fatal error. */
-			DEBUG(0,("EBADF on event_loop_wait - exiting\n"));
+			DEBUG(0,("EBADF on event_loop_once - exiting\n"));
 			return;
 		}