Changes between Version 23 and Version 24 of BasicApi

Timestamp:

Dec 12, 2009, 9:04:41 PM (15 years ago)

Author:

davea

Comment:

--

BasicApi

@@ -262 +262 @@
 == Standalone mode == #standalone
 
-BOINC applications can be run in "standalone" mode for testing, or under the control of the BOINC client. You might want your application to behave differently in the two cases. For example you might want to output debugging information if the application is running standalone. To determine if the application is running in standalone mode or under the control of the BOINC client, call
+BOINC applications can be run in "standalone" mode for testing, or under the control of the BOINC client.
+You might want your application to behave differently in the two cases.
+ For example you might want to output debugging information if the application is running standalone.
+To determine if the application is running in standalone mode or under the control of the BOINC client, call
 
 {{{
@@ -284 +287 @@
 == Requesting network connection == #network
 
-If your application needs to do network communication and it appears that there is no physical network connection (e.g. `gethostbyname()` fails for a valid name) then:
+If your application needs to do network communication and it appears that there is no physical network connection
+(e.g. `gethostbyname()` fails for a valid name) then:
 
   * Call `boinc_need_network()`. This will alert the user that a network connection is needed.
@@ -297 +301 @@
 void boinc_network_done();
 }}}
+
+== Temporary exit ==
+
+If a GPU application fails to allocate GPU RAM, it may be a temporary problem
+(non-BOINC programs have GPU RAM allocated).
+In this case they should call
+
+{{{
+#!c++
+int boinc_temporary_exit(int delay);
+}}}
+
+This will exit the application, and will tell the BOINC client to restart it
+again in at least '''delay''' seconds.
+(This works with 6.10.25+ client;
+on other clients, it will potentially restart immediately).