From ad4b84fd6060d8978e1fd4583a9416706a383a64 Mon Sep 17 00:00:00 2001 From: zimoch Date: Fri, 30 Nov 2007 15:33:22 +0000 Subject: [PATCH] disconnect callback --- doc/businterface.html | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/doc/businterface.html b/doc/businterface.html index 1bc61e7..ff77a01 100644 --- a/doc/businterface.html +++ b/doc/businterface.html @@ -172,6 +172,9 @@ void eventCallback(StreamIoStatus status);
void connectCallback(StreamIoStatus status);
+
+void disconnectCallback(StreamIoStatus status); +

Other provided methods, attibutes, and types

@@ -280,6 +283,9 @@ bool disconnect();
void connectCallback(IoStatus status);
+
+void disconnectCallback(IoStatus status); +

Connection should be handled automatically. If the device is disconnected, each attempt to access the @@ -292,7 +298,8 @@ However, sometimes the client wants to connect or disconnect explicitely. To connect, the client calls connectRequest(). This function should return true immediately -or false if the request cannot be accepted. +or false if the request cannot be accepted or connection +handling is not supported. The interface should call connectCallback(StreamIoSuccess) once the bus could be connected. If the bus cannot be connected within connecttimeout_ms @@ -305,10 +312,14 @@ something wrong with the I/O hardware, connectCallback(StreamIoFault) may be called.

-To disconnect, the client calls disconnect(); +To disconnect, the client calls disconnectRequest(); This function should return true immediately or -false if disconnecting is impossible. -There is no callback for disconnect(). +false if the request cannot be accepted or connection +handling is not supported. +The interface should call connectCallback(StreamIoSuccess) +once the bus is disconnected. There is no timeout for this operation. +If disconnecting is impossible, the interface should call +connectCallback(StreamIoFault).