when to use soap and when to use xml

[Tony Johansson]

Hi!

I'm reading in a book and it says the following.
"Use XML serialization when you need to exchange an object with an
application that might not be based on the .NET Framework, and you do not
need to serialize any private members."

In the book it also says the following.
"Use SoapFormatter when other application might read your seriazed data and
when sending data across a network SoapFormatter also work reliably in
situations where you could choose BinaryFormatter."

So according to these two text sections I can use whichever of SoapFormatter
and XML serializing whan I want
to send data to another app that might not use :NET Framework.
So I find it hard to know when to use SoapFormatter and whan to use XML
serializer.


//Tony

 

[Arne Vajhøj]

I'm reading in a book and it says the following.
"Use XML serialization when you need to exchange an object with an
application that might not be based on the .NET Framework, and you do not
need to serialize any private members."

In the book it also says the following.
"Use SoapFormatter when other application might read your seriazed data and
when sending data across a network SoapFormatter also work reliably in
situations where you could choose BinaryFormatter."

So according to these two text sections I can use whichever of SoapFormatter
and XML serializing whan I want
to send data to another app that might not use :NET Framework.
So I find it hard to know when to use SoapFormatter and whan to use XML
serializer.

Not a particular good description.

XML serialixation can with some effort be read by
other technologies.

If you expose a web service that uses SOAP serialization
somewhere under the hood, then the additional rules
in the SOAP standard combined with the description of the
format in the WSDL file will make it trivial for other
technologies to read the file.

Arne