Lists Home |
Date Index |
Leigh Dodds wrote:
> Personally I *want* new client software, I'm
> actually not that much interested in the means
> of transport so long as it's extensible enough to
> be able to capture a wide variety of data.
But the transport issues, or at least the protocol patterns
that are supported are still important.
You'll want your new client to support at least the following
three fundamental protocol patterns:
1. Messaging. The pattern that was the focus of desktop client
development during the 1970's and 80's. This is the fundamental
pattern of distributed processing and gave birth to email and the
earliest notification systems.
2. Request/Response. Polling... A single request message
followed by a single response message. This is the pattern that took
all our attention during the 90's and whose adoption and deployment
changed the world fundamentally. HTTP, RSS, and many client/server
protocols (i.e. database access, etc) use this pattern.
3. Publish/Subscribe. A single request with multiple
responses. This is the pattern that people are trying to see in RSS
even though it is really Request/Response. Now, "real"
publish/subscribe systems (like PubSub.com) are coming on line on the
open Internet after many years of learning in enterprise and closed
network use. This third protocol pattern, or "Third App" will enable
entirely new applications.