Lists Home |
Date Index |
- From: "Bullard, Claude L (Len)" <firstname.lastname@example.org>
- To: Henrik Frystyk Nielsen <email@example.com>, firstname.lastname@example.org
- Date: Tue, 29 Aug 2000 14:25:42 -0500
Ok for messaging and again, for central standards shared across the
uberSystem. Probably not so
good for database management of applications hosted on that system.
This is a juicy topic for those who like distributed chaos and systems
that run best on the edge of turbulence.
Intergraph Public Safety
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Henrik Frystyk Nielsen [mailto:email@example.com]
In other words, in SOAP, a party declares the features that is either a)
required or b) optional in the message and the receiving end can either
take it or leave it. This mechanism can of course also be used to
negotiate (via some "upgrade" mechanism) jumping to another envelope
namespace entirely which covers adding breaking features to the SOAP
We do therefore not need to have any other versioning model than: "look in