| | 191 | Periodically the client will loop through the feed list and download a feed update. The feed update will be stored in a temporary file and any new items will be added to and old items will be deleted from the existing feed list. |
| | 192 | |
| | 193 | Feed updates are required when the current_time > (last_update + update). |
| | 194 | |
| | 195 | New items are items in which there is not already a matching guid in the existing list. |
| | 196 | |
| | 197 | Old items are items that are marked deleted in the existing list and do not have an entry in the feed update. |
| | 198 | |
| | 199 | === Feed Storage === |
| | 200 | |
| | 201 | All data related to the notification system will be stored in a directory off of the main data directory. |
| | 202 | |
| | 203 | || Item || Naming convention || |
| | 204 | || Feed directory || feeds || |
| | 205 | || Feed list || feed_list.xml || |
| | 206 | || Feed || “feed_” + escape_project_url(feed_url) + “.xml” || |
| | 207 | |