[Tickets #7939] Re: Central content reporting system

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7939
------------------------------------------------------------------------------
  Ticket             | 7939
  Updated By         | Duck <duck at obala.net>
  Summary            | Central content reporting system
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Enhancement
  State              | Accepted
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


Duck <duck at obala.net> (2009-03-12 06:32) wrote:

Going forward with the idea about notification of users as admins, I  
come to a better general solution about driver based notification  
system that support. Currently is implemented in classified an letter.

Features:
driver based (facebook, ticket, mail, letter)
composite processing of multiply drivers
switchable driver purpose: a driver can be configured to notify:  
friends, users or admins. For example ticket system in practical will  
be probably used only to notify code admins, and Facebook only users  
and their friends.
internal driver checks if driver is actually available (if user has  
confirmed or FaceBook app, or a registry call exists...)
send notifications to friends. For example if you would like to in  
invite your friends so see you page content it will send a  
notification to all your FB fends and local friends if you have a  
registry call users/getFriends that returns and array of friend's  
usernames.

Code http://cvs.horde.org/incubator/letter/lib/ Notification*