Hi, I have posted the the fifth and final part of the FedOne Design overview series. This focuses on persistence, specifically where in- memory storage occurs, what information needs to be persisted to restore waves, and possible suggestions for where to commit that information to a persistent store.
Post Here: http://www.angleofsight.com/2010/02/google-wave-federation-part-5/ R, Anthony P.S. - Anthony, thanks for the kind words. On Feb 16, 9:43 pm, Anthony Baxter <[email protected]> wrote: > I'd just like to say that these are very nice and very useful posts, > and I'd like to encourage you to write more of them! > > Thanks very much for the work you've put into them. > > Anthony > > > > > > On Wed, Feb 17, 2010 at 04:59, antwatkins <[email protected]> wrote: > > Hello All, > > > I have posted part 4 in the FedOne Series. This is more of a > > reference that gives you the location in code that corresponds to the > > receipt and execution of messages received in XMPP. If you are > > curious what section of code handles the Wavelet update for example, > > you will see where it is read in as an XMPP packet and stripped and > > also where the WaveServer processes the resulting information. > > > Post Here:http://www.angleofsight.com/2010/02/google-wave-federation-part-4/ > > > R, > > > Anthony > > > On Feb 12, 11:32 am, antwatkins <[email protected]> wrote: > >> Hello All, > > >> I have just posted part 3 in the FedOne series. This one illustrates > >> the object graph produced by the use of Guice in FedOne. I found it > >> quite interesting and helpful to see many of the dependencies in > >> FedOne visualized. I used the Grapher extension in Guice, which > >> served as an input to the 3rd party GraphViz tool. > > >> Post > >> here:http://www.angleofsight.com/2010/02/google-wave-federation-part-3/ > > >> R, > > >> Anthony > > >> On Feb 11, 10:56 am, antwatkins <[email protected]> wrote: > > >> > Hi, > > >> > I'm writing a series of posts to describe how the FedOne code as > >> > released is designed and implemented in code. When I got started I > >> > couldn't find any documents that discussed the structure of the code > >> > at a level higher than the comments found in the individual files. So > >> > I thought an overview of the codebase would be helpful to others. > >> > Here's the post I just published > >> > today:http://www.angleofsight.com/2010/02/google-wave-federation-part-2/. > > >> > R, > > >> > Anthony > > > -- > > 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 > > athttp://groups.google.com/group/wave-protocol?hl=en. > > -- > Anthony Baxter, [email protected] -- 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.
