On Aug 14, 2:52*pm, "Tony Johansson" <johansson.anders...@telia.com>
wrote:
Hello!
I just wonder when is it appropriate to use Xml.
Can somebode give me some guide lines ?
When you have some structured data that you need to serialize (to
save, or to transfer to another application). Particularly when that
data has inherent tree structure.
Also, when you expect your output to be consumed by other parties.
There are many XML-based interoperability solutions that allow to
combine XML inputs and outputs of different components in a system
together with some XSLT/XPath glue.
Assume you have a database and a distributed application that is running on
a LAN network
I just want to know when there is a great advantage to use Xml insted of
other
kind of communication such as distributed object.
This just makes no sense. XML is not a way of communication - it's a
way of serializing data, which can then be communicated, but this is
not related to your question here. You absolutely can send XML via a
remote procedure call - indeed. .NET Remoting can work using SOAP as
an underlying protocol, which is XML-based.