Brief summary of Trecx that even your granny would understand.

The idea behind trecx is two fold:

• we create a reporting service which uses a standardised web-based query interface to interrogate distributed event stores and present back collated tracking data
• we provide a stand alone tracking event store that can be used by tools that do not currently hold tracking data. We will use Aspect Oriented Programming to extract events from this sort of tool and send them to the store.
  

So, in our scenario, the reporting service will interrogate Bodington (our institutional VLE which has its own event store) and the Trecx tracking store, which is holding event data from MVNForum (and say, Jabber, or any old tool that doesn't do this itself).

The AOP will produce an Atom / RSS / SMTP message containing an event list which is posted using HTTP to the tracking store for processing.