[ISSUES] Updated: (JLCP-21) Thread Watch Feature

The following issue has been updated:

    Updater: Matthew Schmidt (mailto:[email protected])
       Date: Thu, 1 May 2003 12:46 PM
    Comment:
won't be that hard to do with the change in the forum backend.
    Changes:
          Fix Version changed from  to 0.7.0 (Shiva)
          Fix Version changed from 1.0.0 (Fangorn) to 
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.jlcp.org/secure/ViewIssue.jspa?key=JLCP-21&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.jlcp.org/secure/ViewIssue.jspa?key=JLCP-21


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JLCP-21
    Summary: Thread Watch Feature
       Type: New Feature

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: Javalobby Community Platform
 Components: 
             Forums
   Fix Fors:
             0.7.0 (Shiva)

   Assignee: 
   Reporter: Matthew Schmidt

    Created: Tue, 7 Jan 2003 11:38 AM
    Updated: Thu, 1 May 2003 12:46 PM

Description:
Allow for a "watch" to be set on any node for any user such that if a descendant of that node is added or updated (deleted?), a callback will be issued.

The mechanism I plan to use for callback will be a property change event. The engine will create a watch based on a user ID and a node ID. When a relevant change occurs, an event including the watch information plus the ID of the added/updated node will be sent to a subscribing object. The engine does not handle email, so the subscribing object must do the actual notification of the user.

Since this subscription must be persistent, it must be renewed at app startup. The watches themselves will persist.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.jlcp.org/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira