Serialization Serialization is the process of converting objects into sequence of bits (that includes the object's data as well as information about the object's type and the types of data stored in the object.) that can be transferred across the network connection. The process of serialization is also called marshaling and opposite to this (recreate the original objects) is called de-serialization or un-marshalling. Java provides the automatic serialization of objects. For serialization, classes of objects must implements the java.io.Serializable interface or “import com.google.gwt.user.client.rpc.IsSerializable; “ Note: Only those objects of classes that implement java.io.Serializable interface can be serialized and de-serialized.
Improving the Serialization Performance • For example, you can reduce the size of the serialized data stream by instructing the run-time serializes to ignore specific fields within your class. Another way to improve performance is to implement the ISerializable interface to gain explicit control over the serialization (and deserialization) process. • Fields that are declared final or transient are not exchanged during RPCs. • You can use attributes to prevent specific fields in your class from being serialized. This reduces the size of the output stream and reduces serialization processing overhead. This technique is also useful to prevent security-sensitive data from being serialized. • RPCs give you the opportunity to move all of your UI logic to the client, resulting in greatly improved performance, reduced bandwidth, reduced web server load, and a pleasantly fluid user experience. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
