EVENT_MEMBER PROPERTIES

PROPERTY	NAME	TYPE	TEXT
#EVENT_MEMBER:EVENT_REF	EventRef	Ref	Reference to the EVENT to which an EVENT MEMBER is related
#EVENT_MEMBER:USER_REF	UserRef	Ref	Reference to the USER who is a participant of the EVENT
#EVENT_MEMBER:READ_MARK_DATE	ReadMarkDate	DATE	Date when the USER last red the EVENT

Read mark logic

The decision about which users have read or not the EVENT are based on the following considerations:

Each individual comment in the EVENT (EVENT_COMMENT) contains the date when it was created
Each user that participates in the EVENT will be registered in the EVENT_MEMBER list reflecting the last date when he 'saw' the EVENT. The client APP must invoke event_set_read_mark () to indicate that the user 'saw' the EVENT.
An EVENT is considered to be 'read' by the active user whenever the last ReadMarkDate for that user is equal or greater that the last comment date

Consider the following participants:

Action
User A creates a new EVENT addressed to user B and writes a comment (EVENT_COMMENT)	The read mark date for user A is updated with the same date than the comment added to the EVENT. The event is considered to be 'read' by user A (because it was generated by himself) The event is considered to be 'unread' by users B and C. Note that user C is not inserted inmediately in the EVENT_MEMBER list. No information about the read status is stored for user D
User B reads the EVENT	The read mark date for user B is updated with the current date so it is considered to be read (because current date is posterior to the date when the las comment was generated)
User C reads the EVENT	The read mark date for user C is updated with the current date so it is considered to be read (because current date is posterior to the date when the las comment was generated)
User D reads the EVENT	No information is modified for User D, as he is not a direct participant of the EVENT
User B adds a comment to the EVENT	The read mark date for user B is updated with the same date than the comment added to the EVENT. So it is considered 'read' by user A The EVENT is considered to be 'unread' by users A and C, because the last read mark date is prior to the last comment date