Fallback daemon doesn't make sense.

2 files changed, 1 insertions, 39 deletions

diff --git a/doc/C-API.txt b/doc/C-API.txt
index cb16ff7..edf0d56 100644
--- a/doc/C-API.txt
+++ b/doc/C-API.txt
@@ -121,22 +121,6 @@ Convenience function that calls dapi_connect() and if successful
 also performs initialization by calling dapi_Init() (see later).
 
 
-DapiConnection* dapi_namedConnect( const char* name )
------------------------------------------------------
-
-Tries to connect to a named fallback daemon.
-
-name: name of the fallback daemon
-Returns: NULL if failed, opaque connection handle if success.
-
-
-DapiConnection* dapi_namedConnectAndInit( const char* name )
-------------------------------------------------------------
-
-Convenience function that calls dapi_namedConnect() and if successful
-also performs initialization by calling dapi_Init() (see later).
-
-
 void dapi_close( DapiConnection* conn )
 ---------------------------------------
 
diff --git a/doc/C-HOWTO.txt b/doc/C-HOWTO.txt
index 3425377..bb0fe97 100644
--- a/doc/C-HOWTO.txt
+++ b/doc/C-HOWTO.txt
@@ -137,29 +137,7 @@ the required functionality.
 No backend daemon running
 -------------------------
 
-A backend daemon should be provided by the desktop environment in which the application is running.
-If dapi_connectAndInit() call fails, it is most probably because the daemon is not available.
-In such case the application may consider shipping its own fallback daemon.
-
-
-int initializeDapi()
-    {
-    my_dapi_connection = dapi_connectAndInit();
-    if( my_dapi_connection == NULL )
-        { /* failure, try a fallback */
-        run_fallback_daemon();
-        my_dapi_connection = dapi_namedConnectAndInit( "MyAppFooInc" );
-        if( my_dapi_connection == NULL )
-            return 0; /* still no luck */
-        }
-    return 1;
-    }
-
-This approach allows silently expecting all following calls to succeed and not caring about fallback
-code at all. (NOTE: still experimental, not sure if it's worth it)
-
-The provided generic daemon accepts --dapiname argument that specifies the fallback name it should
-use. In this specific case run_fallback_daemon() could run "dapi_generic --dapiname MyAppFooInc".
+TODO: fallback daemons don't make sense, the library should try to implement fallbacks
 
 
 Some functionality not available