Collaboration Design Patterns within Groove and SharePoint

I work with Groove and SharePoint and after reading Keith Pleas' posting on 'Collaboration Design Patterns' it has conjured up a lot of good ideas. Both Groove and SharePoint are extendable with Groove tools (using the GDK/GTK) and WebParts (& also web service calls via CAML & lists). I find that "collaboration" is really an amalgamation of several patterns. As a developer it will certainly help decomposing the various patterns and seeing the 'sum of the (pattern) parts'.

Groove's peer-to-peer architecture is inherently different than SharePoint's webserver-centric one but integrating both together (in a Groove Mobile WorkSpace) brings interesting set of results (patterns). Roles within a collaborative space vary - Groove has the 'Manager', 'Participant' & 'Guest' roles and SharePoint has several more ('Author', etc). Roles would determine which particular set of collaborative patterns are invoked. Within a Groove Mobile WorkSpace (that integrates with SharePoint), it is the 'Manager' that synchronizes the Groove space with SharePoint contents (and vice-versa). In addition to Fowler's text, I think I'll have to dig up some of my old textbooks in distributed algorithms (Tel's DA in particular). Something worth looking into..