The Google Wave production services run an indexer which is notified of every change to a wave and continually re-indexes waves as they change. There is an index per user and the indexer counts unread blips for each user and records that in the user's index. The count of unread waves in your inbox, or unread results for any given query, was never done reliably and never worked very well. We were planning to implement reliable counts of unread waves for fixed queries, like "Inbox", "All", saved searches, and folders, by maintaining these counts in the index and incrementing/decrementing the counts whenever we re-indexed a wave.
Soren On Tue, Nov 2, 2010 at 12:55 AM, Torben Weis <[email protected]> wrote: > Hi, > I just read the wave store design: > http://www.waveprotocol.org/protocol/design-proposals/wave-store-design-for-wave-in-a-box > That was very interesting, thanks. > In my own wave server implementation I have a problem with storing the > number of unread-waves/unread-blips. > The current Google Wave UI shows the number of new/changed waves in the > window title and for each wave it shows the number of new/changed blips. > As far as I can see this is not handled in the above document yet. > Currently I see two extreme solutions to my problem > a) Each time a wave/blip changes I update "something" (i.e. databases, inbox > file, what so ever) for each user. > However, if a wave has many users this can become extremely time consuming. > I call this the "push" approach because changes are pushed towards the user > b) The pull approach. When a user starts a wave session, the server pulls in > information about all waves the user is participating in. > This is extremely time consuming on startup. > I noticed that the Google Wave UI uses the "+" trick, i.e. it does not > always show the correct number of new/changed waves and blips. It provides a > lower bound. > I would really like to know which solution Google has taken for this > problem. > Greetings > Torben > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
