All, I have a skeletal prototype of the a rules engine written in Java (i.e. some rules, no UI). I'd like to check I'm heading down the right path. As I see it people should be able to define actions based on the following things coming to their JID; - A message - A subscription request - A conference request The fields of the Jabber data message that affect what action can be taken are; - Who it is from - If the message contains some particular text - If the message subject contains some particular text - If the sender is in the roster or not. - If the user is in a specific group in the roster. And the actions to be performed are; - Forward to another JID (may just be forwarding to another resource on the same JID). - Forward the message to an Email address. - Send a reply message (pulling the data from either a static message, file, or URL). - Drop the message. - Log the message to a file. - (in the case of subscription) accept the subscription request. - Issue a subscription request to the sender. How does this sound? I'll probably have some code up by tomorrow night for people to pull down and play with. Al. _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
