RE: XML versus SOAP/WSDL Performance

["Durham, David" <david.durham@intel.com>]

I don't think performance is the issue for configuration management. Where
as XML is already being used for voluminous ecommerce transactions, I don't
think the comparatively minuscule amount of device configuration data should
raise anyone's eyebrows. Architecturally, it seems that the choice of
sending either (for example):

    A. The entire XML configuration for every minor config update vs.
    B. Delta updates to Named Instances of XML configuration data

Is, IMHO, a much better discussion to have rather how long it takes to parse
a bunch of tagged data.

-Dave

> -----Original Message-----
> From: Steven M. Bellovin [mailto:smb@research.att.com]
>
> >In message <3D8AFD97.5010606@ctit.utwente.nl>, Aiko Pras writes:
> >Hi all
> >
> >Recently I've had a number of discussions on the performance differences 
> >between network management approaches that use XML technology, and 
> >approaches that use web services (SOAP/WSDL). Is there anyone who has 
> >real experience in this area, or know pointers to studies on this?
>
> Is "performance" really the issue?  Is there enough network management 
> traffic that that's an issue?  I'd look more at the architectural and 
> security questions.  (Note, though, that simply saying "XML" is 
> insufficient, since you need to define a transport mechanism.)


--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>