Changes between Version 6 and Version 7 of AppMultiThread

Timestamp:

Nov 20, 2007, 3:44:31 PM (17 years ago)

Author:

Nicolas

Comment:

Comment. Please don't kill me.

AppMultiThread

@@ -67 +67 @@
  * app->core (process control channel): {{{<actual_nthreads>}}}
 
+{{{
+#!comment
+
+*ahem*
+
+Unless, before we get to add multi-threading support, we do the sane thing and change the communication use a compact binary protocol over a pipe instead of XML over shared memory.
+
+"shared memory has to be right below 'printing and scanning with OCR' in terms of favorite means of IPC" -- rtyler on #boinc, irc.freenode.net
+
+By the way, it would be nice to stabilize the API documented here, and implement it as a stub that always tells the app to use 1 thread. That way project developers don't have to wait for BOINC support before making multi-threaded applications. They could create apps supporting multiple threads right now, and whenever the BOINC client (or an unofficial fork, since everything will be so nicely documented, right?) adds support for this, they would Just Work(tm).
+}}}
+
 Client maintains estimates of CPU efficiency per job,
 uses this to scale {{{target_nthreads}}}.
-
 
 Implementation ({{{enforce_schedule()}}}):