A seachengine to retrieve informations from the homepage of the university leipzig. Created during the information retrieval internship in winter semester 2017.
Every Interaction with the system (no matter which) needs to be logged in a centralized way.
Since this is a cross cutting concern, a preferred way to solve this issue would be aspect oriented programming.
Please note that we could change the scope of the ticket in any way. The things that I have mentioned here is only what first comes to my mind and should serve as a discussion base for determining the real scope of what is to be done in the ticket!
Basically, the goal if this ticket is a single aspect, which:
logs response times and request headers and accesed resources for every request
attaches a session cookie to every user
logs:
which queries executed a user
did a user some pagination for a query
which results are clicked by a user
which results are showed to the user
which recommendations are showed to the user
which recommendation are clicked by the user
the preferred way to solve this is:
do everything on the server
dont expect the user is executing javascript
hence rely completely on default browser headers like referrer
Maybe we could use some fancy tools (e.g. not only a single rdbms) like event sourcing (apache kafka, rabbit mq) or stuff like that (that would be really interesting :) )
Every Interaction with the system (no matter which) needs to be logged in a centralized way. Since this is a cross cutting concern, a preferred way to solve this issue would be aspect oriented programming.
Please note that we could change the scope of the ticket in any way. The things that I have mentioned here is only what first comes to my mind and should serve as a discussion base for determining the real scope of what is to be done in the ticket!
Basically, the goal if this ticket is a single aspect, which: