I agree to all of your assertions.
Martin
-----Ursprüngliche Nachricht-----
Von: Alex Rousskov [mailto:rousskov(_at_)measurement-factory(_dot_)com]
Gesendet: Dienstag, 6. Mai 2003 18:54
An: OPES Group
Betreff: Re: Using XML in OCP transport
On Tue, 6 May 2003, Markus Hofmann wrote:
Is parsing a few XML messages for BEEP's channel management such a
big problem that it would justify defining an alternate protocol
over an existing one?
Let me try to distill the question further, in hope to isolate the
subset of XML-related issues that lack consensus. I will phrase these
as assertions:
1 An OCP/BEEP implementation would parse simple,
short XML fragments most of the time.
2 To be compliant, an OCP/BEEP implementation would
have to be able to parse arbitrary XML, including
malicious XML.
3 In 7 years, virtually every OCP/* agent will support XML
for reasons unrelated to transport; that support may not
be efficient (e.g., parsing of configuration files or
generating logs).
4 It is possible to optimize parsing of simple,
short XML fragments with known parsing goal
(e.g., just to find the profile URIs and ignore
everything else).
5 It is possible to optimize generation of simple,
short XML fragments.
6 It is very tempting to use XML for OCP negotiations
and other, mostly performance-unrelated OCP tasks _if_
XML has to be supported for transport reasons anyway.
7 The use of XML will initially alienate a noticeable
fraction of the existing ICAP community
Does anybody disagree with any of the above assertions?
Thanks,
Alex.