On Wed, 9 May 2001, Mark Nottingham wrote:
> The main advantages of XMLizing the invalidation are:
>
> - ability to invalidate multiple resources with one message
> - extensibility, richer semantics
> - overloading HTTP semantics (with a new PURGE method, or by re-using
> DELETE) is problematic and may introduce errors (esp. with
> interception proxies, etc.)
The main disadvantages of XMLizing the invalidation are:
- bloating clients with XML parsers/manipulators
(contradicts thin-client requirement of some protocols)
- spending developers time on writing XML parsers/manipulators
(I doubt there are portable XML libraries appropriate for every
client that is subject to RUP protocols)
- chasing a moving target (some XML-related specs change at such
a rate that it may take years for developers to catch up)
- losing the advantages offered by domain-specific languages
(one size fits all can never fit perfectly)
Just to balance-out the picture...
I am not pro/anti-XML. XML may be the future, but it is not "free" or
ideal choice for every application today. Will XML be the best choice
for every application? I doubt. If it is not going to be, we should
consider each XML application carefully.
$0.02,
Alex.
<PS language="c++">
/home/rousskov/src/xerces-c-src1_4_0/include/util/AutoSense.hpp:197:
#error Code requires port to host OS!
</PS>
<PS language="english">
Apache's Xerces-C library is not supported on FreeBSD yet.
Port it, continue trying different XML libraries, or write your own.
</PS>
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:22:57 MST