A small description of Tim's blog-from-Groove tool. It's almost the inverse of what John Burkhardt is building in Groove Edge Services. Blogger implements Web Services, via a small API, which lets developers use XML-RPC calls to make posts to your weblog. This is "Center Services", if you like: the service is running on a big box at Blogger Central, from where it does cool Blogger things to update web pages on actual webservers (such as this one at cabezal.com).
So, Tim's Groove tool

• lives in a Groove shared space, where there's
• some user interface: a field to write text in, a display of the Web page you're blogging to, and a couple of buttons;
• some storage (on each user's device, synchronized by the magic of Groove) holding an archive of past postings (for no particular reason, I guess, other than because it's possible!)

Now, turn this whole thing inside out, and you'll understand Edge Services. In the edge services model there is no Big Central Server, just a whole lot of PCs (at the edge of the network: behind firewalls, on roaming WiFi connections, DHCP-assigned IP addresses, all the usual garbage - you generally can't find a simple IP address to call into these machines). By building SOAP interfaces to the services these PCs can implement - and there's a whole lot of interesting services they can provide - you get a new world of interop between Groove and Web. The magic sauce is somewhere in the middle, using well-known relay points (multiple, many) to be able to call these devices's services (and receive callback events from them) regardless where the endpoints are.