Re: [xwiki-devs] Issue with installed count on e.x.o overflowing the AS + too many versions

Hi Sergiu, Sure, we could use another store. However the goal of XWiki is also to provide a generic store which can be used to store metadata (through xobjects) related to wiki pages. And install count for an extension really looks like a good metadata candidate for a wiki page. Using another store would also be more work. So, I’d prefer if we could find a way to support this use case which seems legitimate. We have several such use cases, which consist in having some system user perform modifications to wiki pages: * scheduler which updates scheduled jobs with the last fire time xproperty * this extension scheduler which updates install counts * (I’m sure we have more examples but I can’t find one right now ;)) My personal POV is that long term we should have: * Introduce a proper reserved (you cannot create a user named after it) and virtual “System” user (and don’t use “Admin” or “superadmin” which are users which should be used by admins) * Filter out System user changes by default in Activity Stream, History, etc (with options to display them) * Refactor the Versioning store (and possibly get get rid of JRCS) to have a scalable system which supports an unlimited number of revisions without impacting performances * Add an API to merge several revisions into one (this could be useful for auto save too). This is related to what you called “pseudoversion” too: http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Publication+Work… Thanks -Vincent