Originally, back with GWT 1.1 and 1.2, objects that could be serialized across GWT's RPC layer had to implement com.google.gwt.user.client.rpc.IsSerializable. This interface had no methods, it just had to be implemented.
Implementing IsSerializable vs java.io.Serializable was a hassle for those of us with large Java libraries which were used in non-GWT projects. It meant keeping two versions of the code, one implementing IsSerializable, the other Serializable. As I understand, java.io.Serializable carries a lot more baggage than IsSerializable, but for GWT, the extra doesn't matter. GWT programmers just need a way to flag a class as serializable. Thus with 1.3 (I think), the GWT team was good enough to change things so that implementing java.io.Serializable would give us the same result as com.google.gwt.user.client.rpc.IsSerializable. Just use java.io.Serializable. On Jul 20, 11:18 am, Magnus <[email protected]> wrote: > Hi, > > what's the difference between > implements IsSerializable > and > implements Serializable? > > If I have a class that should be used both on the client side and on > the server side, which interface should be used? > > Thanks > Magnus -- 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.
