Applied XML Programming for Microsoft .NET.pdf - Csbdu.in

formatter access the source data through the methods of the ISerializable interface.The formatter obtains raw data that it then packs into the expected output stream.In the alternative serialization model, the DataSet object itself starts and controls theserialization and deserialization process through a group of extra methods. TheDataTable object does not offer public methods to support such an alternative andembedded serialization interface, nor does the DataView object.In the end, both the official and the embedded serialization engines share the same setof methods. The overall architecture of DataSet and DataTable serialization isgraphically rendered in Figure 9-1.Figure 9-1: Both the DataSet object and the DataTable object implement the ISerializableinterface for classic .NET Framework serialization. The DataSet object also publiclyexposes the internal API used to support classic serialization.All the methods that the DataSet object uses internally to support the .NET Frameworkserialization process are publicly exposed to applications through a group of methods,one pair of which clearly stands out—ReadXml and WriteXml. The DataTable object, onthe other hand, does not publish the same methods, although this feature can be easilyobtained with a little code. (I'll demonstrate this in the section "Serializing FilteredViews," on page 417.)As you can see in the architecture depicted in Figure 9-1, both objects always passXML data to .NET Framework formatters. This means that there is no .NET Framework-325