Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4468805

Backward-incompatible change in java.net.Socket when using special SocketImpl.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 1.4.0
    • 1.4.0
    • core-libs
    • beta2
    • generic
    • generic


      Name: bsC130419 Date: 06/12/2001


      java version "1.4.0-beta"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b65)
      Java HotSpot(TM) Client VM (build 1.4.0-beta-b65, mixed mode)

      We have a subclass of SocketImpl and of Socket, for implementing a (proxied)
      protocol that Java doesn't directly support (in this case SSL).

      We call the Socket constructor that takes a SocketImpl to create an unconnected
      Socket, then use TCPSocketImpl to bind and connect. We never use the Socket
      constructors that actually perform a connection.

      In 1.4, it is not possible to proceed in this way, as the Socket methods
      getInputStream() and getOutputStream() both check the state of a private
      boolean flag called 'connected'. In our implementation, this never gets set,
      even though the connection has occurred correctly.

      This means that networking support in 1.4 is not backward compatible with
      earlier releases (1.3, 1.2, 1.1).
      (Review ID: 125093)
      ======================================================================

            jccollet Jean-Christophe Collet (Inactive)
            bstrathesunw Bill Strathearn (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: