Giter Club home page Giter Club logo

Comments (7)

sp-1234 avatar sp-1234 commented on July 18, 2024 2

@TakahikoKawasaki
So did you think about it since that day? 😉

AFAIK these lines

               //     It won't happen unless the programmer dare call
               //     open() and disconnect() in parallel.

are not true because there's also async open method, and there are very valid reasons to do disconnect call while the connection is still opening — for example if user decided to abort the action which required the WS connection, and the only logical thing to do at this point is to terminate the WS connection. And it could be in "opening" state at this moment, if the user is sufficiently fast or the network is sufficiently slow.

from nv-websocket-client.

TakahikoKawasaki avatar TakahikoKawasaki commented on July 18, 2024

Isn't WebSocketFactory.setConnectionTimeout(int) applicable to your case?

from nv-websocket-client.

barelyreal avatar barelyreal commented on July 18, 2024

Not in this case, because sometimes I have to immediately shut down all connections in response to other input.

from nv-websocket-client.

TakahikoKawasaki avatar TakahikoKawasaki commented on July 18, 2024

Calling close() on the raw socket closes the raw socket. What does "sometimes doesn't (work)" mean? What do you expect to happen after close()? I'm sorry I don't understand well what behavior you expect yet.

from nv-websocket-client.

barelyreal avatar barelyreal commented on July 18, 2024

Ah, sorry, when calling close(), the WebSocket object will sometimes continue to open (perhaps the socket hasn't been opened yet), and sometimes will fail to send a CLOSING and CLOSED state.

from nv-websocket-client.

TakahikoKawasaki avatar TakahikoKawasaki commented on July 18, 2024

Thank you. I understood what you meant. Give me some time to think about it.

from nv-websocket-client.

wachidsusilo avatar wachidsusilo commented on July 18, 2024

Any progress on this?
Why can't we close the connection while the state is CONNECTING? Is there any reason I don't understand yet?

UPDATE 14/12/2022:
This is a workaround until this issue fixed. I think the correct implementation would be sending close signal to the polling thread, so that it can stop itself whenever it is convenient.

private lateinit var mClient: WebSocket
...
fun close() {
      val client = mClient;
      CoroutineScope(Dispatchers.IO).launch {
          while (client.state == WebSocketState.CONNECTING) {
              delay(10)
          }
          client.disconnect()
      }
}

from nv-websocket-client.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.