refresh second pass

[Dave Peticolas]

"Phillip Shelton" writes:
> 
> 
> > -----Original Message-----
> > Here is a second pass at a refresh design and API. It's similar
> > to the first, so I won't repost the intro or diagram. It has two
> > major changes:
> >
> > 1. The CM API has been changed so that components specify which
> >    entities they want to watch. Individual entities and whole
> >    classes of entities may be watched. Watches are associated
> >    with gui components, not with callbacks. This avoids having
> >    tons of callbacks for each component.
> >
> >    Being able to register for classes of entities (i.e., you
> >    watch all accounts) makes it easier to start simple and
> >    then refine for efficiency later on.
> 
> That is for things like, I am looking at last months transactions and
> someone else is, or in another window, this months transactions are being
> entered. Does my window get updated if none of the transactions in my window
> are affected?
> sorry about the grammar.

That is intended to address the scalability issue that Derek Atkins
brought up, so that components can specify, e.g., they only need to
be notified if Accounts A, B, and C are modified.

So yes, the idea is that the window only gets a callback if the
specific transactions in the window are changed.

dave