[Xapian-tickets] [Xapian] #295: Add support for multi and remote databases with PostingSources

[Xapian]

#295: Add support for multi and remote databases with PostingSources
-------------------------+--------------------------------------------------
 Reporter:  richard      |        Owner:  richard  
     Type:  enhancement  |       Status:  reopened 
 Priority:  normal       |    Milestone:  1.1.0    
Component:  Matcher      |      Version:  SVN trunk
 Severity:  normal       |   Resolution:           
 Keywords:               |    Blockedby:           
 Platform:  All          |     Blocking:  206      
-------------------------+--------------------------------------------------

Comment(by richard):

 I've added comments about the database passed to posting sources.

 I've made a separate ticket (#336) about the assertion error for
 valueweightsource, so it doesn't get forgotten.

 Looking into externalsource4 now.

 Regarding the namespacing of name(): the lookup of names isn't exactly in
 a performance critical location, so I think having neat and clean code is
 the most important thing.  If performance became a problem, we could
 always do a trick (like defining a custom comparator starting the
 comparison at the 9th character) at a later date.  Therefore, consistency
 with Xapian::Weight is the only reason to change this.  However, I think
 it would be much better to change Xapian::Weight to match this approach.
 There currently aren't likely to be many user weighting classes, and even
 if there are, unless they're using "Xapian::" as the prefix of their name,
 changing our names won't break anything.  We're already changing the
 network protocol, so now's a good time to change Xapian::Weight::name.

-- 
Ticket URL: <http://trac.xapian.org/ticket/295#comment:13>
Xapian <http://xapian.org/>
Xapian