Java serialization - Revision history

M4gnum0n: R section

2012-02-23T16:14:29Z

R section

← Previous revision		Revision as of 16:14, 23 February 2012
Line 1:		Line 1:
	#REDIRECT [[Serialization#Java]]		#REDIRECT [[Serialization#Java]] {{R section}}

116.50.213.210: ←Redirected page to Serialization#Java

2008-10-13T02:00:01Z

←Redirected page to Serialization#Java

← Previous revision		Revision as of 02:00, 13 October 2008
Line 1:		Line 1:
	#REDIRECT [[Serialization]]		#REDIRECT [[Serialization#Java]]

Dysprosia: #REDIRECT Serialization - merged

2004-07-10T04:43:44Z

#REDIRECT Serialization - merged

← Previous revision		Revision as of 04:43, 10 July 2004
Line 1:		Line 1:
			#REDIRECT [[Serialization]]
	Java provides automatic [[serialization]] which only requires that the object be marked by implementing the Serializable interface. For some not-so-clear reason, the process of serialization is handled in a very idiosyntric manner. There are no serialization methods defined on the Serializable interface; implementing the interface just marks the class as "okay to serialize." Java then handles serialization internally, though it does allow the developer to override this by implementing two special methods on a Serializable object. Again, these methods are not defined on the Serializable interface.

	The standard encoding method uses a simple transaltion of the fields into a byte stream. Primitives as well as referenced objects are encoded into the stream. Each object that is referenced by the serialized object must also be serialized and if any in the reference graph is not Serializable, then serialization will fail (unless the developer has redefined the serialization for an object and truncates some portion of the reference graph).

	There is a push to redefine, or provide an alternative to the standard serialization protocol that uses XML and produces a human readable encoding. Such an encoding could be useful for persisted objects that may be browsed by humans or communicated to other, non-Java systems, but the more compact, byte encoding is generally more practical.

195.92.67.76 at 23:01, 23 December 2003

2003-12-23T23:01:57Z

← Previous revision		Revision as of 23:01, 23 December 2003
Line 1:		Line 1:
	Java provides automatic [[serialization]] which only requires that the object be marked by implementing the Serializable interface. For some not-to-clear reason, the process of serialization is handled in a very idiosyntric manner. There are no serialization methods defined on the Serializable interface; implementing the interface just marks the class as "okay to serialize." Java then handles serialization internally, though it does allow the developer to override this by implementing two special methods on a Serializable object. Again, these methods are not defined on the Serializable interface.		Java provides automatic [[serialization]] which only requires that the object be marked by implementing the Serializable interface. For some not-so-clear reason, the process of serialization is handled in a very idiosyntric manner. There are no serialization methods defined on the Serializable interface; implementing the interface just marks the class as "okay to serialize." Java then handles serialization internally, though it does allow the developer to override this by implementing two special methods on a Serializable object. Again, these methods are not defined on the Serializable interface.

	The standard encoding method uses a simple transaltion of the fields into a byte stream. Primitives as well as referenced objects are encoded into the stream. Each object that is referenced by the serialized object must also be serialized and if any in the reference graph is not Serializable, then serialization will fail (unless the developer has redefined the serialization for an object and truncates some portion of the reference graph).		The standard encoding method uses a simple transaltion of the fields into a byte stream. Primitives as well as referenced objects are encoded into the stream. Each object that is referenced by the serialized object must also be serialized and if any in the reference graph is not Serializable, then serialization will fail (unless the developer has redefined the serialization for an object and truncates some portion of the reference graph).

Altenmann: referred to "serialization page" (and moved some text there)

2003-11-27T19:33:55Z

referred to "serialization page" (and moved some text there)

← Previous revision		Revision as of 19:33, 27 November 2003
Line 1:		Line 1:
		⚫	Java provides automatic [[serialization]] which only requires that the object be marked by implementing the Serializable interface. For some not-to-clear reason, the process of serialization is handled in a very idiosyntric manner. There are no serialization methods defined on the Serializable interface; implementing the interface just marks the class as "okay to serialize." Java then handles serialization internally, though it does allow the developer to override this by implementing two special methods on a Serializable object. Again, these methods are not defined on the Serializable interface.
	Serialization is the process of taking an in memory representation of an object and encoding it using a standard format. This encoded version can then be saved to disk, sent across a network connection, or otherwise communicated to another Java virtual machine (or perhaps the same JVM at a different time.

	Serialization is used as a simple way to pesist objects, send messages, or even to distribute objects. There are certainly other ways to accomplish these things, and serialization is often viewed as a quick and dirty method. There are cases, however, where it is perfectly adequate to the task at hand.

⚫	Java provides automatic serialization which only requires that the object me marked by implementing the Serializable interface. For some not-to-clear reason, the process of serialization is handled in a very idiosyntric manner. There are no serialization methods defined on the Serializable interface; implementing the interface just marks the class as "okay to serialize." Java then handles serialization internally, though it does allow the developer to override this by implementing two special methods on a Serializable object. Again, these methods are not defined on the Serializable interface.

	The standard encoding method uses a simple transaltion of the fields into a byte stream. Primitives as well as referenced objects are encoded into the stream. Each object that is referenced by the serialized object must also be serialized and if any in the reference graph is not Serializable, then serialization will fail (unless the developer has redefined the serialization for an object and truncates some portion of the reference graph).		The standard encoding method uses a simple transaltion of the fields into a byte stream. Primitives as well as referenced objects are encoded into the stream. Each object that is referenced by the serialized object must also be serialized and if any in the reference graph is not Serializable, then serialization will fail (unless the developer has redefined the serialization for an object and truncates some portion of the reference graph).

Zanerock at 18:00, 27 November 2003

2003-11-27T18:00:32Z

New page

Serialization is the process of taking an in memory representation of an object and encoding it using a standard format. This encoded version can then be saved to disk, sent across a network connection, or otherwise communicated to another Java virtual machine (or perhaps the same JVM at a different time.

Serialization is used as a simple way to pesist objects, send messages, or even to distribute objects. There are certainly other ways to accomplish these things, and serialization is often viewed as a quick and dirty method. There are cases, however, where it is perfectly adequate to the task at hand.

Java provides automatic serialization which only requires that the object me marked by implementing the Serializable interface. For some not-to-clear reason, the process of serialization is handled in a very idiosyntric manner. There are no serialization methods defined on the Serializable interface; implementing the interface just marks the class as "okay to serialize." Java then handles serialization internally, though it does allow the developer to override this by implementing two special methods on a Serializable object. Again, these methods are not defined on the Serializable interface.

The standard encoding method uses a simple transaltion of the fields into a byte stream. Primitives as well as referenced objects are encoded into the stream. Each object that is referenced by the serialized object must also be serialized and if any in the reference graph is not Serializable, then serialization will fail (unless the developer has redefined the serialization for an object and truncates some portion of the reference graph).

There is a push to redefine, or provide an alternative to the standard serialization protocol that uses XML and produces a human readable encoding. Such an encoding could be useful for persisted objects that may be browsed by humans or communicated to other, non-Java systems, but the more compact, byte encoding is generally more practical.