Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Do Qt's network operations support constant streaming of data?
Forum Updated to NodeBB v4.3 + New Features

Do Qt's network operations support constant streaming of data?

Scheduled Pinned Locked Moved General and Desktop
2 Posts 2 Posters 1.1k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    codewriter
    wrote on last edited by
    #1

    I'd like to use Qt to get streaming data from a Trading Brokerage.

    I'm using KQPAuth library, but it's unclear if Qt's NetworkManager will allow me to make an authenticated request(this it will do) and then just leave the socket open for constant streaming data based on my one request(Can I do this?).

    This is an issue apart from the KQPAuth library.

    Apparently, TradeKing brokerage will give me the ConsumerKey, ConsumerSecretKey, ACCESS_TOKEN, and ACCESS_TOKEN_SECRET outside of any network requests.

    All I have to do is send 1 authenticated request for specific stock data, and then leave the connection/socket open and just monitor all data coming to me in a never-ending stream.

    The real question is whether or not the NetworkManager supports Not closing a steam after 1 reply is received.

    I'd like to use the signal/slot paradigm to notify whenever a new "chunk" of data comes through the stream.

    If I can do this, then how?

    1 Reply Last reply
    0
    • C Offline
      C Offline
      ChrisW67
      wrote on last edited by
      #2

      I am assuming your "1 authenticated request" is an HTTP GET or POST. If the server never closes the connection and you don't close the QNetworkReply object then the connection stays open. Any additional data sent by the server will cause additional readyRead() signals from the QNetworkReply object.

      If the request is not an HTTP transaction then QTcpSocket may be more appropriate.

      I have no idea what a KQPAuth library is (even Google doesn't) or what it might have to do with anything.

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved