XML Serialization | Binary Serialization (Soap) |
No need of Serializable attribute on the class | Need Serializable attribute |
Only public members are serialized | All members are serializes unless specified as NonSerializable |
Class should have default public constructor and class itself should have public access. | No need of default constructor or public access |
Namespace: System.XML,Serialization | Namespace: System.Runtime.Serialization.Formatteres.Binary (.Soap) |
Outputfile is XML | Outputfile is Binary or XML for SOAP formatter |
XMLSerializer need type of object to be serialized or deserialized | No need to specify type of object to be serialized or deserialized. |
Support only IDesrializationCallback interface. No support for binary events. | Binaryformatter support binary events. Soap formatter supports only IDeserializationCallback interface |
HTML5 has introduced lots of new cool tags . Not all the browsers support all tags and also the implementation of these tags may be different for each browser. HTML5 specification defines the functional aspects of these tags and not the implementation. Also the general concensus is that by 2022 all browsers will support all new features of HTML5. Of all the modern browsers, Chrome seems to have implemented most, if not all, featutes of HTML5. IE9 supports few. Firefox sits in between. So as a developer how do you make use of the cool HTML5 features without causing any compatibility issues with existing browsers? Traditionally developers have used User Agent to detect browser type and use the features accordingly. However these days, you can easily change a User Agent by using addons in your browser. So you need a more robust way to detect the features supported by the browser as the same engine of two different versions of a browser mig...
Comments