[ISSUES] Work Logged: (JLCP-21) Thread Watch Feature
[email protected] Tue, 27 May 2003 23:05:58 -0400 (EDT)
| Newsgroups | gmane.comp.java.javalobby.communityplatform |
|---|---|
| Message-ID | <[email protected]> |
The following work log has been added to this issue:
Logged By: Matthew Schmidt
Created: Tue, 27 May 2003 11:04 PM
Time Logged: 2 hours
Description:
ok, we can click on an image next to a forum in AllTopics to add a new forum watch. We can also click on an image next to a thread subject in TopicDetails. Then there is a page in the useragent that lets you view your watches. From there you can remove a watch. We'll test once the UI works again.
---------------------------------------------------------------------
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: Assigned
Priority: Major
Time Spent: 2 hours
Estimate: 0 minutes
Project: Javalobby Community Platform
Components:
Forums
Fix Fors:
0.7.0 (Shiva)
Assignee: Matthew Schmidt
Reporter: Matthew Schmidt
Created: Tue, 7 Jan 2003 11:38 AM
Updated: Tue, 27 May 2003 11:04 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