Changes between Version 11 and Version 12 of SPIDocs


Ignore:
Timestamp:
Sep 16, 2014 11:42:11 AM (8 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SPIDocs

    v11 v12  
    216216Many operations in the SPI require a user to agree with the operation before the operation becomes final.  Users who wish to join a project or a circle request permission from the users who own or administer them.  Administrators who wish to add users to their circles request confirmation from the users.  Basically any operation that expands the rights of users requires the users in question to concur.  In order to let users know when such changes are pending or desired, the SPI supports a system for managing short messages available through the `Users` [wiki:SPIDocs#Services service].
    217217
    218 ''Notifications'' are these short messages.  A notification consists of a the text of the message a unique identifier for the message, and a set of flags.  The valid flags are:
     218''Notifications'' are these short messages.  Notifications are sent by the system in response to actions requiring confirmation.  This is not a general inter-user messaging system.
     219
     220A notification consists of a the text of the message a unique identifier for the message, and a set of flags.  The valid flags are:
    219221
    220222||= Flag Name =||= Meaning =||
     
    222224|| Read || The user has read this message ||
    223225
    224 Flags are specified when a notification is sent and can be set by the receiver as well.
    225 
     226
     227Each user has a queue of notifications they can access.  The `getNotifications` operation on the `Users` service returns an array of notifications for an application to display.  Notifications can be filtered by source and by flags.  The flags can be set using the `markNotifications` operation that specifies notifications by unique ID.
     228
     229Applications will use these operations to:
     230
     231 * Present a user with a list of pending notifications when a user logs in, or at regular intervals.
     232 * Display urgent and other notifications differently.
     233 * Allow users to read and respond to notifications by calling avrious SPI operations to confirm pending actions
     234 * Search notifications for past actions
     235 * Mark notifications as read once viewed and acted upon
     236
     237Note that users generally cannot send notifications to other users.  Only administrators and testbed actions do this.
     238