ADO.NET and Xml
Question posted by: Tony Johansson
(Guest)
on
August 20th, 2008 10:35 AM
Hello!
I'm reading in a book and here it says the following.
ADO.NET uses the open Internet-standard XML format for communications
between the tiers,
allowing data to pass through Internet firewalls and allowing the
possibility of non-Microsoft
implementation of one or more tiers.
I just wonder you can't say that Xml is used as an open Intenet-standard for
communications between tiers
because if you use distributed object then you will not use Xml.
Can somebody if I haved missed something here.
//Tony
5
Answers Posted
Can you cite the source so we have context?
It really depends on the meaning... for example, the heart of ADO.NET is
going to be talking to databases, and that is going to be proprietary (TDS
for example). I suspect that this line is referring to transfer of DataSets
over web-boundaries via web-services - where indeed it uses xml - and
DataSet (etc) support IXmlSerializable. However, you'd be hard-pressed to
say that DataSet is standards-friendly - using a DataSet on a public-facing
web-service would not be good: it is hard for non-.NET clients to consume
it.
As an aside: it was a gripe originally that a DataSet, when serialized with
BinaryFormatter, simply did the xml serialization and stored the string
(larger than necessary); this has (IIRC) now changed, so DataSet will also
serialize to a proprietary binary form via BinaryFormatter (ISerializable).
Re distributed object, do you mean remoting? Remoting can use a range of
transports, but is .NET specific anyway. If you use WCF you have more
options, but I still wouldn't *generally* use DataSet etc on a WCF boundary.
I have on occasion (for unknown schema scenarios with .NET clients), but not
as a rule...
Marc
Hello!
Here is the exact text from the book.
"ADO.NET uses the open Internet-standard XML format for communications
between the tiers, allowing data to pass through Internet firewalls and
allowing the
possibility of non-Microsoft implementation of one or more tiers."
//Tony
"Marc Gravell" <marc.gravell@gmail.comskrev i meddelandet
news:%23fOgCtqAJHA.908@TK2MSFTNGP03.phx.gbl...
Quote:
Originally Posted by
Can you cite the source so we have context?
>
It really depends on the meaning... for example, the heart of ADO.NET is
going to be talking to databases, and that is going to be proprietary (TDS
for example). I suspect that this line is referring to transfer of
DataSets
Quote:
Originally Posted by
over web-boundaries via web-services - where indeed it uses xml - and
DataSet (etc) support IXmlSerializable. However, you'd be hard-pressed to
say that DataSet is standards-friendly - using a DataSet on a
public-facing
Quote:
Originally Posted by
web-service would not be good: it is hard for non-.NET clients to consume
it.
>
As an aside: it was a gripe originally that a DataSet, when serialized
with
Quote:
Originally Posted by
BinaryFormatter, simply did the xml serialization and stored the string
(larger than necessary); this has (IIRC) now changed, so DataSet will also
serialize to a proprietary binary form via BinaryFormatter
(ISerializable).
Quote:
Originally Posted by
>
Re distributed object, do you mean remoting? Remoting can use a range of
transports, but is .NET specific anyway. If you use WCF you have more
options, but I still wouldn't *generally* use DataSet etc on a WCF
boundary.
Quote:
Originally Posted by
I have on occasion (for unknown schema scenarios with .NET clients), but
not
Quote:
Originally Posted by
as a rule...
>
Marc
>
>
That still doesn't really allow me to understand exactly what it is talking
about at that point... oh well. Anyway, does my earlier reply make any
sense?
Marc
Yes It's enought for me!
//Tony
"Marc Gravell" <marc.gravell@gmail.comskrev i meddelandet
news:uS7Ap6qAJHA.3628@TK2MSFTNGP05.phx.gbl...
Quote:
Originally Posted by
That still doesn't really allow me to understand exactly what it is
talking
Quote:
Originally Posted by
about at that point... oh well. Anyway, does my earlier reply make any
sense?
>
Marc
>
>
Tony Johansson wrote:
Quote:
Originally Posted by
I'm reading in a book and here it says the following.
ADO.NET uses the open Internet-standard XML format for communications
between the tiers,
allowing data to pass through Internet firewalls and allowing the
possibility of non-Microsoft
implementation of one or more tiers.
>
I just wonder you can't say that Xml is used as an open Intenet-standard for
communications between tiers
because if you use distributed object then you will not use Xml.
>
Can somebody if I haved missed something here.
ADO.NET does use XML in general.
You can use XML with distributed objects as a transport format.
It is in most cases a bad design to expose raw data services - you
should instead expose more high level services.
Arne
|
|
|
What is Bytes?
We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights.
Get the best answers to your questions from over 197,031 network members.
Top Community Contributors
|
