Mike,
1. Yes, you are right. The most we've ever needed to do in production is a few million matches per second. The 3 billion/second number is what we get in testing.
3. re: mod-pubsub support. We used a slightly modified version of our REST support to feed messages to KnowNow LiveServers. I believe the mod-pubsub interfaces are very similar to KnowNow's. The KnowNow/mod-pubsub technology is very useful since it allows us to establish a light-weight, persistent, firewall-piercing connection to the desktop. Our focus is on the matching problem and we're pleased to be able to leverage existing solutions to actually do delivery of messages. Let's talk offline in email about working with mod-pubsub.
5. It would take too long to explain in a comment, however, let me just say that a number of methods for computing "relevance" of matches rely on examining the history of messages that have been delivered to a particular subscription over time as well as on user feedback. Thus, even if two subscriptions have identical queries, they may deliver different results based on when they were created and the user's history of interaction with the results. If we don't provide a binding between a user and a subscription, we will be severely limited in our ability to implement a whole class of improved methods for determining the "relevance" of a matched item. This would not be a good thing. The "single step" solution that you propose works very well with retrospective searches (i.e. what Google, Feedster, etc. do) where the entire result set is available each time the query is re-evaluated. However, this solution is much less useful in a "prospective" system like we implement since in such a system, the result set accumulates over time and we can benefit from user interaction and hinting over time.
bob wyman
|
Previous Message
Up
