Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-16688

Behaviors of socket class waitFor*() inconsistent

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P2: Important P2: Important
    • None
    • 4.5.0
    • Network: Sockets
    • None

      [Note: Re-raised from QT-1185, originally reported by Oswald Buddenhagen]

      In QLocalSocket, on windows, waitForReadyRead() will not return soon when the socket was already disconnected.

      On unix, it will return false even if buffered data is still available after it was disconnected (i would expect this to be possible unless the disconnected state is not entered until all data was read - the docs unfortunately do not say anything about synchronization of read and disconnect, unlike write and disconnect).

      On unix, waitForDisconnected() will complain when already disconnected, on windows it won't (the former seems bogus to me).

      I have checked only a few functions. i suggest a full audit in that regard of both QLocalSocket and QAbstractSocket.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Unassigned Unassigned
            jasmcdon Jason McDonald (Closed Nokia Identity. Please assign to "macadder" instead) (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                There are no open Gerrit changes