Changes between Version 24 and Version 25 of Notifications
- Timestamp:
- Nov 3, 2009, 12:31:26 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Notifications
v24 v25 70 70 || application_only || false || Feed is used by an application and should not be shown in BOINC Manager or the BOINC Screen saver. || 71 71 72 == Notification Flag Supported == 73 Clients that support the BOINC Notification System should include the following flag: 74 {{{ 75 <notifications_supported /> 76 }}} 77 78 When the BOINC Server scheduler sees this flag it’ll include extra information in the scheduler reply that is to be included in the BOINC Client Feed stream. 79 80 == BOINC Client Feed Stream == 81 The BOINC Client feed stream is a special in memory RSS feed the BOINC Client software maintains for various user interface components. 82 83 BOINC Server scheduler replies can add items to the feed stream as well as the client itself. 84 72 85 == Server Scheduler == 73 86 The server scheduler is responsible for aggregating the various pieces of information about feeds and pushes the result to the client as part of the scheduler reply. A similar process is used for the GUI URLs. … … 79 92 80 93 If an empty result set is returned by the database, then pass the contents of feeds.xml unmodified. 81 82 === Notification Supported Flag ===83 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.84 85 Notification flag:86 {{{87 <notifications_supported />88 }}}89 94 90 95 === Scheduler Reply === … … 161 166 162 167 == BOINC Core Client == 163 === Scheduler Request ===164 Add the notification flag to the request protocol:165 166 {{{167 <notifications_supported />168 }}}169 168 170 169 === GUI RPCs === … … 191 190 192 191 '''Notes''': 193 * If both project_url and feed_url are empty, the BOINC clientstream is returned.192 * If both project_url and feed_url are empty, the BOINC Client Feed stream is returned. 194 193 * Requests for private feeds should return an error. 195 194 * This RPC should not require authentication.
