pair
14:11  * JeffreyH wonders if stearns saw his private chat a few minutes ago, given 
          his spiffy new IRC client
14:11 <stearns> yes, but I was slow to type there :-)
                 monitors don't know about y's
14:12 <ovaltofu> they only notice changes to masters/modifs that have y's
14:12 <ovaltofu> sorry x's
14:13 <gbaillie> well, the dynamically inherited object is always y's master, and we 
                                                                                     
                 only care about modifications
14:14 <ovaltofu> so, x changes on a modifications and we want to re-index all 
                 dependent occurrences ?
14:14 <ovaltofu> limiting the problem a bit
14:14 <ovaltofu> ?
14:14 <gbaillie> Usually, it's that x changes on the master, and we want to re-index 
                 the dependent occurrences
14:15 <ovaltofu> you just said " the dynamically inherited object is always y's 
                 master, and we only care about modifications"
14:15 <ovaltofu> I'm confused
14:15 <ovaltofu> anyway, the problem is the same
14:15 <ovaltofu> the monitors won't know magically to trigger the re=indexing of the 
                 dependents
14:15 <ovaltofu> but they'll notice the change to the master/modif
14:16 <gbaillie> The only "dynamical inheritance" is from occurrences to masters.
14:16 <ovaltofu> and the method invoked can do the right thing in propagating that
14:16 <ovaltofu> one sec, door rang
14:16 <gbaillie> If you change a mod, you changed the mod. If you change the master, 
                 everything else changes.
14:17 <ovaltofu> back
14:17 <ovaltofu> ok
14:18 <ovaltofu> so the question is "how to re=index 'everything else' when a master 
                 changes" ?
14:18 <gbaillie> not just reindex.
14:18 <ovaltofu> yes, also send notifs
14:18 <ovaltofu> ?
14:18 <gbaillie> Right
14:19 <ovaltofu> focusing on just re-indexing for a minute, though
14:19 <gbaillie> (assuming that's how the detail view and dashboard notice attribute 
                 changes)
14:19 <ovaltofu> well, they only watch one particular item at a time so they can use 
                 other tricks
14:19 <gbaillie> right, true
14:19 <ovaltofu> we may not need to broadcast notifs to a 100 occurrences if only 
                 one matters
14:20 -!- reid[osaf] [n=rae@tnir.org] has quit ["rebooting into pure windows"]
14:20 <ovaltofu> but reindexing needs to be done for all these, at once
14:20 <ovaltofu> via moveKeys
14:20 <ovaltofu> so, when the monitor watching the master's x attribute fires
14:20 -!- JeffreyH_ [n=chatzill@c-24-7-82-42.hsd1.ca.comcast.net] has joined 
          #recurrence
14:21 <ovaltofu> it needs to find all occurrences (at least their ids), their 
                 collections, and call re-index on the relevant indexes
14:21 <JeffreyH_> sigh.  Comcast had a hickup, apparently.  Can someone pastebin 
                  history for me, this time?
14:21 <stearns> I will.