"method level" serializable ServerSockets

Question

i don't understand why this code block can be serialized:
public class Foo extends Thread implements Serializable {
  public void run() {
    ServerSocket servSok = new ServerSocket(9876);
    Socket sok = servSok.accept();
}compare with this code block. as expected it cannot serialize (unless transient is used):
exception code = " +NotSerializableException: java.net.ServerSocket+ "
public class Foo extends Thread implements Serializable {
  private ServerSocket servSok = null;  // <-- add "transient" and ok.
  public void run() {
    this.servSok = new ServerSocket(9876);
    Socket sok = servSok.accept();
note: both are live, running, threads when serialized.
one is an instance level object, the other a method level. but i cannot take my understanding
beyond that. can someone talk me through what is going on?
both are bound ServerSockets . neither can pop-up, after de-serialization, bound to a port
on a remote jvm.

Answer 1

pdFrog wrote:
Your misunderstanding is that methods do not get serializedok. i did not know that.
i think this is why we need the class loaders.Mneh, in a roundabout way, but probably not the way you're thinking. Technically speaking, methods are already serialized, in that their bytecode exists as a stream. But if you're trying to serialize code, not just data, you've probably misunderstood why we serialize. In particular, serializing a Socket connection of any kind is a bit pointless.