Hi Jeremie, On Fri, Jul 18, 2014 at 5:58 PM, Jeremie BOUSQUET < [email protected]> wrote:

Hello,

2014-07-18 16:32 GMT+02:00 Eduard Moraru <[email protected]>:

...

Hi devs,

As part of the investigation on the Activity Stream Refactoring for the 6.2 roadmap, I have written a couple of documents [1] on some of the problems (specifically performance [2]) of the current implementation and also tried to list various use cases [3] that a better AS implementation should support.

I would like to ask you to: - help out in listing possible use cases [3] that I have missed or you`d like AS to support,

One use-case I thought about, but it's really nice-to-have IMO, could be to allow choosing a specific "display" (or "theme", or "displayer" ...) for the macro results. Possible displays or themes could be: - default (the current one) - livetable - timeline ... Obviously, granularity of details could not be the same depending on the chosen theme, but it would be ok if maximum details are show in the "default" (current) view. And you could provide custom ones if needed. It's maybe overkill, compared to duplicating the macro to an as_timeline or as_livetable macro ...

Interesting as a nice-to-have feature. Do you have any particular actual use case for such a feature in mind? What would be the benefit of displaying the events in a different view? I find the livetable view not very useful. Also, having a custom display would basically mean rewriting the macro completely, since the macro is 95% UI. Perhaps the only functionality that you would reuse would be indeed the filtering (through macro parameters), though that too would be fairly easy to replicate. Thanks for the quick reply so far. Keep them coming! :) -Eduard

...

- offer your opinion on my current findings [1] and/or - share your thoughts on where should we go with the new implementation of AS.

Thanks, Eduard

---------- [1]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62

...

[2]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62P...

...

[3]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62U...

...

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

2014-07-18 19:24 GMT+02:00 Jeremie BOUSQUET <[email protected]>:

Hi,

2014-07-18 18:47 GMT+02:00 Eduard Moraru <[email protected]>:

Hi Jeremie,

...

On Fri, Jul 18, 2014 at 5:58 PM, Jeremie BOUSQUET < [email protected]> wrote:

...

Hello,

2014-07-18 16:32 GMT+02:00 Eduard Moraru <[email protected]>:

...

Hi devs,

As part of the investigation on the Activity Stream Refactoring for the 6.2 roadmap, I have written a couple of documents [1] on some of the problems (specifically performance [2]) of the current implementation and also tried to list various use cases [3] that a better AS implementation should support.

I would like to ask you to: - help out in listing possible use cases [3] that I have missed or you`d like AS to support,

One use-case I thought about, but it's really nice-to-have IMO, could be to allow choosing a specific "display" (or "theme", or "displayer" ...) for the macro results. Possible displays or themes could be: - default (the current one) - livetable - timeline ... Obviously, granularity of details could not be the same depending on the chosen theme, but it would be ok if maximum details are show in the "default" (current) view. And you could provide custom ones if needed. It's maybe overkill, compared to duplicating the macro to an as_timeline or as_livetable macro ...

Interesting as a nice-to-have feature.

Do you have any particular actual use case for such a feature in mind? What would be the benefit of displaying the events in a different view? I find the livetable view not very useful.

I agree with you for livetable view, but I was trying to find more than 2 alternatives ;-) There is no specific use-case for a "timeline" view in this case, except that a timeline can be pretty, and fun (for the user, not so much for the devs ...). It would be, obviously, a pure UI gadget, and an UI customization alternative for your dashboards for example.

... also, current stream is vertical, whereas a timeline is usually horizontal, so it provides different UI integration possibilities.

...

Also, having a custom display would basically mean rewriting the macro completely, since the macro is 95% UI. Perhaps the only functionality that you would reuse would be indeed the filtering (through macro parameters), though that too would be fairly easy to replicate.

The only use-case I can see for keeping 1 macro, maybe, would be that you could easily customize it (when included in a dashboard for example), by just editing it inline and choosing a different value for the "theme" parameter. It's slightly more user-friendly than having to include another macro. In fact it would be easier in wiki mode than in wysiwyg in this case. But, to start with, providing an alternate macro for a timeline view could do the trick.[OFF] I have some hopes to provide a simile timeline extension some day ... but still never found time to do it.[/OFF]

...

Thanks for the quick reply so far. Keep them coming! :) -Eduard

...

...

- offer your opinion on my current findings [1] and/or - share your thoughts on where should we go with the new implementation of AS.

Thanks, Eduard

---------- [1]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62

...

...

[2]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62P...

...

...

[3]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62U...

...

...

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

Hi Paul, On Sat, Jul 19, 2014 at 1:04 AM, Paul Libbrecht <[email protected]> wrote:

Hello Eduard,

It's funny that this happens right now, while we are fiddling in the ActivityStream (of XWiki 3.5.1, as subclassed by curriki). We are doing so to offer notifications for gpsnetwork.org: daily digests and immediate.

So the first request is to enable a hook for immediate notification (a groovy page?) and digest notifications, I find.

Why exactly are you subclassing ActivityStream to achieve that? Why not use XWiki`s Observation Modules [1]? That`s what AS uses to immediately catch events and store them. You can do the same for immediate notifications. For daily digests, just use a daily scheduler job and get the recorded events from AS for the day that just passed. Also, how exactly are you using the events to offer "notifications"? Can you offer more details? On a related topic, would you find it interesting to have the output of the activity macro (with your filters/parameters applied to it) as JSON so that you would use it in your application? Would a REST (xml/json output) resource for reading events be better instead of a macro in a wiki page? ---------- [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Observation+Module+Loca...

What I like in the use-cases is the notion of grouping (this tastes like a transaction id of some sort):

This is already supported by the current AS implementation, but in a crude way. Basically, all events have a requestID [2] (or group [3][4] if you`re using eventstream's API). The current implementation of this is to assign an ID to the current request and pass that ID to all the events generated in the same request, by using/sharing the same XWiki context. It is in the right direction, but if you do a lot of stuff (programatically) in the same request, it is too noisy and becomes not relevant. It is useful for UI actions though, as they tend to be more focused than programatic ones. There still remains the problem of prioritising the events within the same group/request, which is not solved yet. ---------- [2] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwik... [3] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwik... [4] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwik...

I am sure we can make use of this in various places, including the way to track the series of save operations that happen when you create a document or resource (currently, Curriki has a minimum version numbers and, not surprisingly, one one of them was wrong).

Can you offer more details on this?

The big deal of performance and extensibility sounds quite hard to me. They are opposed to each other. We know that the ActivityStream can be hogged and we would avoid relying on it if we create some intensive event stream (e.g. in some form of analytics); nonetheless, the performance sounds reasonable thus far. Extensibility cannot happen thus far. We have… param1, param2, …, param5. And that is almost enough (we started to add one of them to be a json record to get more space!). The problem with extensibility is the storage form: If you add an event type, you add a hibernate mapping.

Curriki has wrapped events for this: they are created based on param1, …, param5 and document names, when the stream is displayed.

When pondering real hard core analytics, we have been considering a few alternatives, e.g. CouchDB or MongoDB. But this has never made its way. I am convinced Solr would do the trick too. Somehow, there must be storage forms that take advantage of the very peculiar nature of the event streams: - only inserts, no updates - reads that can be application defined, and probably can assert that an amount of events is not useful anymore.

As for the all the research about the macro, we stay way from that, since Curriki has its own set of UIs.

Ok, so we are talking about a storage level extensibility here. More exactly, how to support various (new) event type's parameters [5]. Please see my comment on that issue [5] about using a list of parameters (instead of the problematic map and of the current param1..param5 implementataion). Would that help towards a decently performant extensibility improvement? Going for a NoSQL solution just for this problem might be a bit of overengineering... Thanks, Eduard ---------- [5] http://jira.xwiki.org/browse/XWIKI-7554

Paul

On 18 juil. 2014, at 16:32, Eduard Moraru <[email protected]> wrote:

...

Hi devs,

As part of the investigation on the Activity Stream Refactoring for the 6.2 roadmap, I have written a couple of documents [1] on some of the problems (specifically performance [2]) of the current implementation and also tried to list various use cases [3] that a better AS implementation should support.

I would like to ask you to: - help out in listing possible use cases [3] that I have missed or you`d like AS to support, - offer your opinion on my current findings [1] and/or - share your thoughts on where should we go with the new implementation of AS.

Thanks, Eduard

---------- [1]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62

...

[2]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62P...

...

[3]

http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62U...

...

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs