I can easily hack this in for demo purposes (for ApacheCon?) and send it to you. For a demo, anything goes.
Actually here it is, attached. More permanently -- I'm reluctant to add logic like "if userID is specified then it means recommend() and if itemID is specified then it means mostSimilarUsers()" since it kind of seems to preclude using userID or itemID later for params to other methods. It feels as if one determines which method is being called on a class just based on parameters. The web services interface is supposed to be the 'real' interface for more sophisticated integration and it supports this, or could easily. This style of integration -- or any other -- is certainly possible, and strikes me as more robust, when it comes to Solr or whatever. More on that later indeed. Sean On Fri, Mar 20, 2009 at 6:40 PM, Grant Ingersoll <[email protected]> wrote: > I'm mostly looking for more along the lines of "demoability" than any > particular API for interacting programmatically. I already have it in my > mind that Taste will be integrated w/ Solr at some point in the not too > distant future, such that one will then be able to combine CF w/ Search and > Faceting and get all of Solr's goodness for response writers, custom > components, etc. Not to mention, I'm sure a some would love to see > relevance factors based on ratings, etc. > > Just thinking out loud, > Grant
