1. Jan 04, 2019
  2. Oct 01, 2018
  3. Aug 14, 2018
  4. Aug 10, 2018
  5. Sep 26, 2017
  6. Apr 27, 2017
  7. Sep 07, 2016
  8. Mar 10, 2016
  9. Jan 20, 2016
  10. Sep 04, 2015
    • Peter Kümmel's avatar
      Set parent of internal socket objects · e8335d48
      Peter Kümmel authored
      After moving the websocket into another thread
      current code doesn't work because then the QTcpSocket/QSslSocket
      objects reside in a different thread, for instance:
      "QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread"
      
      QObject::moveToThread(QThread*) also moves QObjects's children,
      therefore their internal socket objects need to be children of QWebSocket.
      
      QWebSocket has ownership of the internal socket, and the
      smart pointer is not needed any more.
      
      Change of cleanup code to prevent crashes with clang/msvc builds:
      QWebSocketPrivate is a scoped member of QObject (not QWebSocket)
      and is destroyed after QObject destructor body was executed,
      and so  m_pSocket&co had already been destroyed (being children)
      when the destructor of QWebSocketPrivate is called via the
      scoped pointer.
      
      Analogous to 64927e04
      
      
      
      Change-Id: I1ade6cda3fa793c30332cc5e103025e2dda3c78c
      Reviewed-by: default avatarLuca Niccoli <lultimouomo@gmail.com>
      Reviewed-by: default avatarAlex Blasche <alexander.blasche@theqtcompany.com>
      e8335d48
  11. May 26, 2015
  12. Apr 08, 2015
  13. Feb 16, 2015
  14. Nov 19, 2014
  15. Aug 24, 2014
  16. Mar 17, 2014
  17. Feb 15, 2014
  18. Feb 05, 2014
  19. Feb 04, 2014
  20. Feb 01, 2014
  21. Jan 20, 2014
  22. Jan 17, 2014
  23. Jan 12, 2014
  24. Jan 11, 2014
    • Kurt Pattyn's avatar
      Remove waitXXX() methods from websockets · b019b9cc
      Kurt Pattyn authored
      
      The QWebSocketServer::waitForNewConnection() was just calling
      QTcpServer::waitForNewConnection(), which was not correct because
      a connection is only complete when the handshake succeeds.
      Waiting for the handshake to complete would need a separate thread
      for the handshake handling code, which would complicate the code a lot.
      It was decided to leave out all waitXXX() methods from the module,
      as it is easier to add this functionality later, then to remove it.
      
      Change-Id: I778bae45b67f81e151ad2362f772c75e9f537ff0
      Reviewed-by: default avatarKurt Pattyn <pattyn.kurt@gmail.com>
      b019b9cc
  25. Dec 23, 2013
  26. Dec 10, 2013
    • Kurt Pattyn's avatar
      Cleanup code to comply with Qt style · 7d35f5c6
      Kurt Pattyn authored
      
      - Correct placement of curly braces
      - Remove commented-out code
      - Remove superfluous qDebug statements
      - Add missing QT_BEGIN_NAMESPACE declarations
      - Add move semantics
      - Add cleanup handling to QWebSocketServerPrivate
      - Add error handling to handshake response, QWebSocketServerPrivate,
        QWebSocketServer, dataprocessor
      
      Change-Id: I0690dc2c444fd6fc0db974d1459bf41bd8c31d40
      Reviewed-by: default avatarKurt Pattyn <pattyn.kurt@gmail.com>
      7d35f5c6
  27. Nov 18, 2013
  28. Nov 17, 2013
  29. Nov 04, 2013
  30. Nov 01, 2013
  31. Oct 31, 2013
  32. Oct 11, 2013
  33. Sep 29, 2013