B4J Question Server handler class (websocket handler class) instance.

[LucaMs]

When a client connects to my server (B4J - jServer) an instance of a "server handler class" is automatically created (it "receives" a websocket object too).

In some cases I want to disconnect the client:

    ' Asks client for its "configuration".
    RunClientRoutine("rtnFromServerSendMeConfig", Null)
' HERE I DON'T WANT TO WAIT INDEFINITELY...
    ' Client sent its "configuration".
    Wait For FromClient_ClientConfig(Params As Map)

' the same when I will wait for user's credentials.

After ' HERE I DON'T WANT TO WAIT INDEFINITELY...
I'm thinking to add a "timeout" (https://www.b4x.com/android/forum/threads/b4x-waitforwithtimeout-timeouthandler.110703/ - I "changed" it to a b4xlib, now).
But... what to do when time runs out?
I can only close the websocket and "exit", which means that I will not add the instance to a global Map.
The instance will be automatically killed sooner or later, right?



P.S. I have to change that b4xlib, B4XTimeoutHandler because it can use a label (B4XView), B4J websocket server not.

 

[LucaMs]

Solved (maybe)

Once the WebSocket has disconnected then it will be released (assuming that you are not holding a reference yourself).

"Maybe" because I "need" to destroy the server handler instance, not (only) the websocket, but I think "it's the same" (same reasoning).

 

[TILogistic]

Comment:

[B4X][B4XLib] WaitForWithTimeout --> TimeoutHandler

I have read many times the request for a "Wait For" with the addition of a timeout. This class is an attempt to implement that functionality. It is a B4X class, in the sense that it can be used with B4A, B4J and B4i; after all it uses only one B4XView which is completely optional and almost...

www.b4x.com

 

[LucaMs]

Thank you, @oparra, but... I know that thread; I created it

 

[TILogistic]

Thank you, @oparra, but... I know that thread; I created it

Yeah it was just to remind you

 

[Erel]

You don't need to do anything special. The class instance will be released after WebSocket disconnects. It doesn't actively waits for anything.