Lisa (Dusseault) and I spoke to Ray at When 2.0 about SSE. SSE is defined at the level of abstract item replication; it's not a network access protocol and is mute on those issues. That is, it addresses how to replicate an RSS feed to have two or more instances which are kept in sync with each other. It detects conflicts but leaves it entirely up to the client to decide what to do. Typically, SSE would be implemented by publishing a feed to a server and handling subscriptions to that feed but in theory there could be P2P implementations. SSE permits feeds to have multiple writers, so the terms "publish" and "subscribe" are a bit misleading. SSE adds unique ID's for items to RSS feeds. Because SSE was meant for different Microsoft applications and services such as Outlook and MSN to share calendar items, it has been assumed that each app would deal with all of the messy implementation details not defined in SSE itself. SSE itself is incomplete as a standard and doesn't address issues of what happens if two clients are trying to write to the feed simultaneously, for instance. So for SSE to be a useful public standard, these aspects would have to use an existing standard or borrow from one. It would certainly be possible for a WebDAV server to be used to support SSE with a modest amount of work. Since RSS support is in the queue for Cosmo, it makes sense for us to follow SSE development carefully, and consider adding support if it looks like SSE is gaining momentum outside Microsoft. Apologies for any lack of technical precision. I'm sure Lisa can amplify and correct as needed. On Dec 8, 2005, at 8:59 AM, Alec Flett wrote:
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
