Socket class - javadoc not sufficiently explicit

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P5
    • None
    • Affects Version/s: 1.4.2
    • Component/s: core-libs
    • x86
    • linux

      FULL PRODUCT VERSION :


      ADDITIONAL OS VERSION INFORMATION :
      n/a - documentation issue

      A DESCRIPTION OF THE PROBLEM :
      People new to sockets often get this wrong..


      bool Socket.isConnected()
      what the javadoc should say:
      Initially this method returns false. After a connection is established, this method method returns true. It will never change back to false for any reason (like the connection failing).

      bool Socket.isClosed()
      what the javadoc should say:
      Initially this method returns false. After Socket.close() is invoked this method returns true. It will not return true for any other reason (like the connection being closed by the remote end).


      REPRODUCIBILITY :
      This bug can be reproduced always.

            Assignee:
            Jean-Christophe Collet (Inactive)
            Reporter:
            Nelson Dcosta (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: