What is Groove Edge Services?

Wow, this is certainly a lively crew.. but what should I have expected?  I'm sure enough people have said enough about what weblogs can do so I'll refrain, suffice to say that my mind is a bit blown right now.  I'll have to get out on my bike later and try to get over it. 

Anyway, to clarify my previous post a bit: I'm really looking for pointers, ideas, on a technical level of how to explore ways of opening up Groove to different environments and devices.  I'm not really in the position to take a bunch of feature requests for specific things.  I'm kind of down in the trenches so to speak.  But I also think that what we are attempting with Edge Services is somewhat new - hey I guess this is all kind of a new medium for a lot of us.  Just be aware that if we (as in we bloggers) come up with some really wacky and wonderful ideas, I'm going to absorb them into my subconcious for a while and we shouldn't count on them becoming a product anytime soon.  However, part of this initiative is to deliver an API that we can play with so I'd love to know how people want to play.

Here are some of the goals:

• Provide a way to access and update information in a Groove Shared Space
• Provide a way to subscribe to certain events.
• Provide a way for the Groove developer to add this functionality to their own tools.

The event part is turning out to be the hardest.  How does a client application receive them?  Do they poll a Relay queue?  Do they implement a web service that I can call?  Do we invent some other protocol that would require the client to have more of our code?

Anyway, its all good stuff.  I'm really going to be interested to see what people can do with it.  And I'm hoping that we can invent new ways of communicating and collaborating that combine some of the best of these new mediums - blogs, google, Groove...

Is it just me or does it seem like we have such a long way to go?  We are cavemen.