Re: End user session tracking
16 okt 2007 kl. 17.12 skrev Ryan McKinley: So I'll start with an ad hoc session manager within Solr. Where in Solr should I add such a service? I am using a custom filter that extends SolrDispatchFilter. Alright, thanks! -- karl
Re: End user session tracking
So I'll start with an ad hoc session manager within Solr. Where in Solr should I add such a service? You may be able to get what you need with just installing something like clickstream: http://www.opensymphony.com/clickstream/ If you need to integrate custom user handling and solr requests, you are definatly in "solr - beyond the box" territory... For session tracking, I am using a custom filter that extends SolrDispatchFilter. This overrides: protected void execute( HttpServletRequest req, SolrRequestHandler handler, SolrQueryRequest sreq, SolrQueryResponse rsp) { // a custom filter could add more stuff to the request before passing it on. // for example: sreq.getContext().put( "HttpServletRequest", req ); sreq.getCore().execute( handler, sreq, rsp ); } In that function, I add the logged in user to the request context and various custom handlers use that. ryan
End user session tracking
Where in Solr would I add my own services? Do I really want to do that? For reinforcement learning reasons I would like to keep track of all queries placed during an end user session, and as it expires I want to feed this information to an aggregated class used by a request handler. I belive it makes more sense to keep track of this session data in Solr rather than in the Solr client code. But then there is the possible future distribution and replication. It would make sense if all nodes would share the same session handler. So perhaps it makes more sense if this was some stand alone service? Perhaps that is pre emptive optimization and I should really just focus on getting my code running first? So I'll start with an ad hoc session manager within Solr. Where in Solr should I add such a service? -- karl