Not a dumb question at all. I like exposing more functionality -- more methods, really -- through the web interface. At the moment the servlet supports basically one method call -- recommend().
Actually, the web services interface exposes all the methods you see on Recommender, so it does more than recommend() already. It raises two questions in my mind -- Should we expose more methods through the simple servlet interface? We'd concoct a scheme for passing many params and selecting which method to invoke. It begins to come close to reinventing SOAP, but perhaps exposing a couple methods is worth it. The point of the servlet interface has been to provide the one core piece of functionality -- recommendations -- in a way that a client could use without a whole SOAP library. Heck you could use this in a BASH script as is with a combination of wget and cut and so on... Should the SOAP interface expose more? Right now it exposes just what "Recommender" exposes, and the particular method you mention is on ItemBasedRecommender, since it makes more sense in that context. I'd have to think about how to dynamically expose methods based on what the caller-provided implementation can do, or whether to push some of those methods up to Recommender. Thoughts or ideas welcome there. On Fri, Mar 20, 2009 at 5:59 PM, Grant Ingersoll <[email protected]> wrote: > Yes, this one, but the others are good to know, too. I'm still a pretty new > to CF, so bare w/ my dumb questions. I was thinking I'd like to be able to > do something like > http://localhost:8080/mahout-taste-webapp/RecommenderServlet?itemID=15 (instead > of userId=?) > > and it would give me back all the movies that are similar to movie 15.
