Our application uses applet-servlet communication through serialized java objects. On the server side we have to use jdk 1.2 or higher. On the client browser we are restricted to jdk 1.1 since most browsers support it w/o plug-in. Problem 1: Servlet to applet communication Objects generated and serialized by the jdk 1.2 VM on the server are read and used successfully in our jdk 1.1 applet *so far*. It's understood the receiving applet is restricted to 1.1 methods (e.g. using 'compareToIgnoreCase()' of class String would be illegal). Problem 2: Applet to servlet communication Certainly a jdk 1.3 servlet receiving serialized objects should not try to use any jdk 1.1 methods on it that vanished in jdk 1.3. Question: Are there more restrictions or potential problems on this? Any experiences with larger projects?
I know this is in prinicpal no solely servlet related question since it might be based on jdk version conflicts and serialisation in general. But i suppose people running servers that require jdk 1.2 or later could also have faced that problem. Wolfgang Stein
Is this the real life? Is this just fantasy? Is this a tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop