What kind of serialization method should be used

  • Thread starter Thread starter Tony Johansson
  • Start date Start date
T

Tony Johansson

Hello!

Assume there are two applications developed in .NET running in two different
networks that should use serialize/deserialized data between each other.
What kind of method should be used.. There are two alternatives
1. BinaryFormatter
2. Soapformatter

According to the docs it says. You should choose BinaryFormatter only when
you know that all clients opening the serialized data will be .NET Framework
applications.
Use SoapFormatter when other applications might read your serialized data
and when sending data across a network.

//Tony
 
Tony said:
Hello!

Assume there are two applications developed in .NET running in two different
networks that should use serialize/deserialized data between each other.
What kind of method should be used.. There are two alternatives
1. BinaryFormatter
2. Soapformatter

According to the docs it says. You should choose BinaryFormatter only when
you know that all clients opening the serialized data will be .NET Framework
applications.
Use SoapFormatter when other applications might read your serialized data
and when sending data across a network.
Click to expand...

Didn't you just answer your own question?
 
Harlan Messinger said:
Didn't you just answer your own questio
Click to expand...

I would assume that using BinaryFormatter would be the best choice but
because we are sending across network
there is also a possibility that SoapFormatter can be used.

So is there a best choice in this matter

//Tony
 
Assume there are two applications developed in .NET running in two different
networks that should use serialize/deserialized data between each other.
What kind of method should be used.. There are two alternatives
1. BinaryFormatter
2. Soapformatter

According to the docs it says. You should choose BinaryFormatter only when
you know that all clients opening the serialized data will be .NET Framework
applications.
Use SoapFormatter when other applications might read your serialized data
and when sending data across a network.
Click to expand...

When it is .NET - .NET then BinaryFormatter will work and it has
a lot less overhead than SoapFormatter, so you should follow the
docs.

If you ever plan on saving in file or database, then I would
suggest XmlSerializer.

Arne
 
Back
Top