[Xapian-tickets] [Xapian] #340: PostingSource subclasses cannot signal a change in their maxweight

[Xapian]

#340: PostingSource subclasses cannot signal a change in their maxweight
-------------------------+--------------------------------------------------
 Reporter:  richard      |        Owner:  olly     
     Type:  defect       |       Status:  new      
 Priority:  normal       |    Milestone:  1.1.1    
Component:  Library API  |      Version:  SVN trunk
 Severity:  normal       |   Resolution:           
 Keywords:               |    Blockedby:           
 Platform:  All          |     Blocking:           
-------------------------+--------------------------------------------------

Comment(by richard):

 Interesting ideas: I think having the posting source specify the new
 maxweight is a good idea (but they still need to make sure that a call to
 get_maxweight returns the new maxweight, as well - unless we take
 get_maxweight out of the API alltogether, and just have a method for
 notifying a new one, which would normally be called from the init method
 to set an initial value).

 I think asking the subclass to supply both old maxweight and the new
 maxweight is just going to result in a lot of duplicated code in
 subclasses - I can't think of a situation where the old one is naturally
 available already.

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