[xwiki-devs] Some kind of DocumentChangedListener? - xwiki-devs@xwiki.org

Sergiu Dumitriu

3 Apr 3 Apr

2:40 a.m.

Lilianne E. Blaze wrote:

Hello, Is there any way to add some code without recompiling xwiki-core (plugin? component?) that could register a listener for any changes in documents (preferably by mask / type, as in "listen for added comments on Main.* and Blog.*") and optionally veto (and/or flag for review?) them? If not, please consider adding it - it would be a very nice way to make writing things like spam- and vandal- filters easier. It would also allow making such things more modular - if any plugin could register such a listener, then there could be (for example) two independent plugins running at once, one handling scenarios like "bad source" - "bad ip", "possible anonymous proxy", the other "bad content" - "bad words", "structure looks like spam" or "too many links".

Yes, there is the old notification API in xwiki-core, and the new observation component that handle this scenario (see http://maven.xwiki.org/site/xwiki-core-parent/xwiki-core-observation/apidoc… for the documentation, and http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-localization/s… for usage example at the end of the file). And yes, this is one of the (three) best approaches to the anti vandalism project. The veto-ing part is not yet written, I remember proposing it initially, but Vincent opposed the idea, and we didn't need it until now. The strategy for developing components is to write the essential functionality first, and add features when the need occurs, so this veto mechanism might be added soon. -- Sergiu Dumitriu http://purl.org/net/sergiu/

Reply

Sergiu Dumitriu

11:21 a.m.

Lilianne E. Blaze wrote:

...

Sergiu Dumitriu wrote:

Lilianne E. Blaze wrote:

Hello, Is there any way to add some code without recompiling xwiki-core (plugin? component?) that could register a listener for any changes in documents (preferably by mask / type, as in "listen for added comments on Main.* and Blog.*") and optionally veto (and/or flag for review?) them? If not, please consider adding it - it would be a very nice way to make writing things like spam- and vandal- filters easier. It would also allow making such things more modular - if any plugin could register such a listener, then there could be (for example) two independent plugins running at once, one handling scenarios like "bad source" - "bad ip", "possible anonymous proxy", the other "bad content" - "bad words", "structure looks like spam" or "too many links".

Yes, there is the old notification API in xwiki-core, and the new observation component that handle this scenario (see http://maven.xwiki.org/site/xwiki-core-parent/xwiki-core-observation/apidoc… for the documentation, and http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-localization/s… for usage example at the end of the file). And yes, this is one of the (three) best approaches to the anti vandalism project. The veto-ing part

What are the other two?

Since the GSoC selection is not yet over, I'll keep this for myself until tomorrow. -- Sergiu Dumitriu http://purl.org/net/sergiu/

Reply

Sergiu Dumitriu

11:16 a.m.

Vincent Massol wrote:

...

On Apr 3, 2009, at 2:40 AM, Sergiu Dumitriu wrote:

Lilianne E. Blaze wrote:

Hello, Is there any way to add some code without recompiling xwiki-core (plugin? component?) that could register a listener for any changes in documents (preferably by mask / type, as in "listen for added comments on Main.* and Blog.*") and optionally veto (and/or flag for review?) them? If not, please consider adding it - it would be a very nice way to make writing things like spam- and vandal- filters easier. It would also allow making such things more modular - if any plugin could register such a listener, then there could be (for example) two independent plugins running at once, one handling scenarios like "bad source" - "bad ip", "possible anonymous proxy", the other "bad content" - "bad words", "structure looks like spam" or "too many links".

Yes, there is the old notification API in xwiki-core, and the new observation component that handle this scenario (see http://maven.xwiki.org/site/xwiki-core-parent/xwiki-core-observation/apidoc… for the documentation, and http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-localization/s… for usage example at the end of the file). And yes, this is one of the (three) best approaches to the anti vandalism project. The veto-ing part is not yet written, I remember proposing it initially, but Vincent opposed the idea,

Sergiu, could you find the email thread again? I'd like to see why I "opposed" the idea.

http://markmail.org/message/fizvsadfge5yurik -- Sergiu Dumitriu http://purl.org/net/sergiu/

Reply