Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. How to specify the web socket port when using the WebGL platform?
Forum Updated to NodeBB v4.3 + New Features

How to specify the web socket port when using the WebGL platform?

Scheduled Pinned Locked Moved Unsolved QML and Qt Quick
6 Posts 2 Posters 1.9k 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.
  • J Offline
    J Offline
    JasonWong
    wrote on 14 Dec 2017, 04:24 last edited by
    #1

    I successfully run the webgl platform on ubuntu16.04, it works great.
    I found that at least two ports should be listen at run time, except primary port (webgl:port=12345), the second port which looks like it is prepared for web socket?
    This port is random, and each time the program started, port not the same, how should I specify this port?

    R 1 Reply Last reply 15 Dec 2017, 12:55
    0
    • J JasonWong
      14 Dec 2017, 04:24

      I successfully run the webgl platform on ubuntu16.04, it works great.
      I found that at least two ports should be listen at run time, except primary port (webgl:port=12345), the second port which looks like it is prepared for web socket?
      This port is random, and each time the program started, port not the same, how should I specify this port?

      R Offline
      R Offline
      raven-worx
      Moderators
      wrote on 15 Dec 2017, 12:55 last edited by raven-worx
      #2

      @JasonWong
      looking at the sources of the plugin a simple QWebSocketServer is created without setting a port at all. Thus a random free port is used.
      Also there is no setting yet available.

      What exactly is your problem? Firewall related?

      Maybe it's a good idea to file feature-request

      --- SUPPORT REQUESTS VIA CHAT WILL BE IGNORED ---
      If you have a question please use the forum so others can benefit from the solution in the future

      J 1 Reply Last reply 15 Dec 2017, 14:47
      0
      • R raven-worx
        15 Dec 2017, 12:55

        @JasonWong
        looking at the sources of the plugin a simple QWebSocketServer is created without setting a port at all. Thus a random free port is used.
        Also there is no setting yet available.

        What exactly is your problem? Firewall related?

        Maybe it's a good idea to file feature-request

        J Offline
        J Offline
        JasonWong
        wrote on 15 Dec 2017, 14:47 last edited by
        #3

        @raven-worx
        Thanks Reply
        Firewall related is one of the problems

        The current WebGL platform supports only single process for single user, I want to make a multi-process manager for multi-user access.
        This requires port management, which can be very troublesome if I can not changed web socket ports.

        R 1 Reply Last reply 15 Dec 2017, 15:45
        0
        • J Offline
          J Offline
          JasonWong
          wrote on 15 Dec 2017, 14:57 last edited by
          #4

          I submitted a suggestion
          https://bugreports.qt.io/browse/QTBUG-65232

          1 Reply Last reply
          0
          • J JasonWong
            15 Dec 2017, 14:47

            @raven-worx
            Thanks Reply
            Firewall related is one of the problems

            The current WebGL platform supports only single process for single user, I want to make a multi-process manager for multi-user access.
            This requires port management, which can be very troublesome if I can not changed web socket ports.

            R Offline
            R Offline
            raven-worx
            Moderators
            wrote on 15 Dec 2017, 15:45 last edited by
            #5

            @JasonWong said in How to specify the web socket port when using the WebGL platform?:

            The current WebGL platform supports only single process for single user, I want to make a multi-process manager for multi-user access.

            i believe i've read that this is planned already.
            But i don't know if it comes with 5.11 or later.

            --- SUPPORT REQUESTS VIA CHAT WILL BE IGNORED ---
            If you have a question please use the forum so others can benefit from the solution in the future

            J 1 Reply Last reply 15 Dec 2017, 15:59
            0
            • R raven-worx
              15 Dec 2017, 15:45

              @JasonWong said in How to specify the web socket port when using the WebGL platform?:

              The current WebGL platform supports only single process for single user, I want to make a multi-process manager for multi-user access.

              i believe i've read that this is planned already.
              But i don't know if it comes with 5.11 or later.

              J Offline
              J Offline
              JasonWong
              wrote on 15 Dec 2017, 15:59 last edited by JasonWong
              #6

              @raven-worx
              I found that blog
              http://blog.qt.io/blog/2017/07/07/qt-webgl-streaming-merged/

              Once it’s ready, you will be able to create an application server to launch different process inheriting the web socket to communicate with the browsers. This will allow for supporting more than one concurrent user instead of sharing applications among users.

              No scheduled time or qt version
              T.T

              1 Reply Last reply
              0

              1/6

              14 Dec 2017, 04:24

              • Login

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