PHP allows serialization and deserialization of whole objects. If untrusted input is allowed into the deserialization function, it is possible to overwrite existing classes in the program and execute malicious attacks. Such an attack on Joomla was found in 2013.
|
|
XML-binary Optimized Packaging (XOP) is a mechanism defined for the serialization of XML Information Sets (infosets) that contain binary data, as well as deserialization back into the XML Information Set.
|
|
Generally ASN.1 tools will include constraints checking into the generated serialization / deserialization routines, raising errors or exceptions if out-of-bounds data is encountered. It is complex to implement all aspects of ASN.1 constraints in an ASN.
|
|
Suitable programming languages are, e.g., Python, C++, and Java. In this approach, writing and reading QuakeML documents is equivalent to serializing/deserializing QuakeML objects to/from their XML representation. A further possibility would be the serialization/deserialization to/from SQL for persistent storage in a relational database.
|
|
For example a process might receive data as a string that presents data a JSON object. Before the data can be used it needs to be unmarshalled into a map data structure, or something more complex. Unmarshalling (similar to deserialization) is the reverse process of marshalling.
|
|
In computer science, pointer swizzling is the conversion of references based on name or position to direct pointer references. It is typically performed during the deserialization (loading) of a relocatable object from disk, such as an executable file or pointer-based data structure. The reverse operation, replacing pointers with position-independent symbols or positions, is sometimes referred to as unswizzling, and is performed during serialization (saving).
|
|
There are alternatives to `clone()`, notably the use of a copy constructor - a constructor that accepts as a parameter another instance of the same class - or a factory method. These methods are not always adequate when the concrete type of the cloned object is not known in advance. (However, `clone()` is often not adequate either for the same reason, as most abstract classes do not implement a public `clone()` method.) Also the use of serialization and deserialization is an alternative to using clone.
|
|
The author goes inside highly- collaborative organizations including Boeing, Toyota, the Dow Chemical Company, Procter & Gamble, DreamWorks Animation, Industrial Light & Magic, the Myelin Repair Foundation, and the Mayo Clinic. He explains how their methods can create value in almost any industry. The book also describes the trend towards real-time, spontaneous collaboration and the deserialization of interaction and work. In his preface, Rosen explains that his idea for the book originated when he was invited to the BMW engineering center in Munich during the final design stage for the X5 sports activity vehicle.
|
|
In computer science, marshalling or marshaling is the process of transforming the memory representation of an object to a data format suitable for storage or transmission, and it is typically used when data must be moved between different parts of a computer program or from one program to another. Marshalling is similar to serialization and is used to communicate to remote objects with an object, in this case a serialized object. It simplifies complex communication, using composite objects in order to communicate instead of primitives. The inverse of marshalling is called unmarshalling (or demarshalling, similar to deserialization).
|
|
An object that is serialized is in the form of a byte stream and it can eventually be converted back to a copy of the original object. Deserialization is the process of converting the byte stream data back to its original object type. An object that is marshalled, however, records the state of the original object and it contains the codebase (codebase here refers to a list of URLs where the object code can be loaded from, and not source code). Hence, in order to convert the object state and codebase(s), unmarshalling must be done.
|
|
FlatBuffers is a free software library implementing a serialization format similar to Protocol Buffers, Thrift, Apache Avro, SBE, and Cap'n Proto, primarily written by Wouter van Oortmerssen and open-sourced by Google. Like Cap'n Proto and SBE, it supports “zero-copy” deserialization, so that accessing the serialized data does not require first copying it into a separate part of memory, which makes accessing data in these formats much faster than data in formats requiring more extensive processing, such as JSON, CSV, and in many cases Protocol Buffers. Compared to other serialization formats however, the handling of FlatBuffers requires usually more code, and some operations are not possible (like some mutation operations). FlatBuffers is a popular project on GitHub, with 10,228 stars, 260 contributors, 1,605 forks, and 600 watchers on GitHub as of 2018-09-19.
|
|