This is used for members of groups if they want waves addressed to that groups indexed directly into their index (think "inbox"). Waves are always indexed into the groups address, this edge is used to signal what other indexes to write the content of the wave in.
This edge setting is a little bit implementation specific in its current form so we probably won't standardize it in this form. For example a wave provider can use read fan out instead (all groups of a user are read at the same time) or a even a global index of waves. Nevertheless the purpose is fairly clear: "Do I want waves from this group in my inbox." This setting is common with mailing lists too. Google Groups for example has a setting on your membership whether you want email sent to you or whether you want to read the messages in the list archive instead. On Wed, Sep 2, 2009 at 7:11 PM, sim-sim<[email protected]> wrote: > > Little misunderstanding about next description: > > "Indexed to (INDEX) - wavelets addressed to address B will be written > into the index of the account associated with address A > (transitively)." > > Whats a typical scenario using in future this edge (in depth)? How it > will be presented in wavelets owner and paticipant, for example? > > Secondary question: Where issue tracker for this and other whitepapers > errors or inconsistencies? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
