Changes between Version 10 and Version 11 of Notifications

Timestamp:

Nov 3, 2009, 9:44:54 AM (15 years ago)

Author:

romw

Comment:

Begin conversion of User Messages into a notification feed

Notifications

@@ -78 +78 @@
 If an empty result set is returned by the database, then pass the contents of feeds.xml unmodified.
 
+=== Notification Supported Flag===
+When the scheduler receives the notification flag it should add any user messages to the BOINC client feed by including a channel and a new item for each user message.
+
+Notification flag:
+{{{
+<notifications_supported />
+}}}
+
+=== Scheduler Reply ===
+User messages generally contain information the volunteer needs to know such as there isn’t enough disk space allocated to the project to run a task instance, or they weren’t assigned any work because they ran out of quota.
+
+Messages like a project being out of work should not be included in the notification stream.
+
+Where possible, notification messages should contain information on how to correct the problem.
+
+Channel items:
+{{{
+<channel>
+    <item>
+        <description>I need more disk space</description>
+        <pubDate>Mon, 30 Sep 2002 01:56:02 GMT</pubDate>
+        <guid>http://www.example.com/1</guid>
+    </item>
+    <item>
+        <description>I need more memory</description>
+        <pubDate>Sun, 29 Sep 2002 19:59:01 GMT</pubDate>
+        <guid>http://www.example.com/2</guid>
+    </item>
+</channel>
+
+}}}
+
+|| Item Elements || Default value || Description ||
+|| description || <null> || An xml encoded message that the volunteer needs to act on ||
+|| pubDate || <scheduler reply time> || RFC 822 representation of the scheduler reply time ||
+|| guid || <null> || Unique message ID prefixed with the master URL of the project ||
+
 == Project Website ==
 A project’s website is the main focal point for adding and removing notification feeds.