Re: [xwiki-devs] [XWIKI-14119] Propositions about in-page notifications design

On Thu, May 18, 2017 at 9:20 AM, Clément Aubin <clement.aubin(a)xwiki.com> wrote: Because xobjects are stored while events are temporary objects by definition. You then have a event/activity stream listener which use the database to cache events to remind users about them but it's really just caching, not infinite storage like xobjetc are. * keeping them as XObject forever is totally useless and does not scale for very frequent events * it duplicates what is already stored in the event stream table * many kind of events are generated by some code and calling something like $services.notification.sendEvent('mytype', $data) make much more sense than having to create some xobject when you want to send an event in your script If the only use case you have in mind is events related to the creation of some kind type of documents (like a blog post) then you should at the very least separate the event descriptor xobject (which would be defined in the document of the blog post xclass for example) and the xobject used as helper to generate an event (since in this use case it's not so easy to have a script called when the document is created) which would be in the saved blog post document. Still it's quite crappy (you still store something to generate a temporary object) and it would be much cleaner (and a lot easier for the application) to have something more dynamic. For example a generic listener on Java side which listen to XObjectAddedEvent and if the xclass document of this xobject contains an event descriptor, automatically send a corresponding event. No useless stiff stored and no need for the application to remember to add a special object every time it create a new entry. -- Thomas Mortagne