PureBasic Forums - English

Sorry it seems there is no SetCancelButtonLabel() Method, or I can't find it.
https://learn.microsoft.com/en-us/windo ... uttonlabel

I confirm, at the moment my server is handling 280 simultaneous TLS connections without problem.

I think I found where the problem is coming from. It seems that the mixing of TLS and non-TLS clients connecting to the TLS server is the cause. Since changing the port for about a hundred clients and the server, only TLS clients are connecting, and I no longer have issues with dialogue loss on the ...

idle, I tested the keepalive setsockopt option server side and client side a few days ago (didn't mention it sorry) and unfortunately it doesn't fix the problem.

PBJim, I'm working on LAN. And for now, I don't have separate loops to handle TLS and non TLS clients. I will change the port on TLS ...

Ok, the more I dig, the more I'm lost...

I tested by modifying the client/server example from PB doc to keep client connection up and sent every 15/30/60 seconds a string to the TLS server : no problem detected.

Then I went back to my program and removed the TLS security from the client and the ...

I found a new problem (since I activated TLS).
My console application, a client-like connected to the server ( permanent connection ) can't communicate with the server after 15-30 seconds of inactivity. However the console is not disconnected from the server.
If I reinitialize the connection ...

I moved the delay(10) inside the Case 0 so that it only waits in that specific scenario. Maybe one day I will figure out why this error occurs...

That's the one I'm using.

Here is some feedback.

Because my tcp server was using recv and send socket functions, I rewrote everything and now i'm using internal PB functions through your wrappers Receive/SendNetworkDataEx().
Everything is working great without TLS : 320 clients + 1 admin console at peak simultaneous ...

Hi,

I'm curious about the behaviour of those network functions when the connection parameter is not valid anymore.
I'm working on a TCP client/server (=~ 250 simultaneous connected clients) and if a client disconnects when a working thread try to send data to it, crash happens. I have to check ...

Question for idle :

How would you handle with SendNetworkDataEx() a message > 65536 bytes ?

I asked the same question to Copilot and it seems most of the time the best method to test a socket availabilty is to send a empty message.
The problem with SendNetworkData() is if the ClientID (socket) is not accessible, it crashes the application (invalid memory access) instead of returning an ...

Try this Quin :
Procedure Is_Socket_Available(SocketHandle)

CompilerIf #PB_Compiler_OS = #PB_OS_Windows
Protected name.SOCKADDR
Protected namelen = SizeOf(SOCKADDR)

If getpeername_(SocketHandle, name, @namelen) <> 0 ; on a une erreur
Debug WSAGetLastError_()
ProcedureReturn 0
Else ...

Thank you very much idle.
I was testing your previous version of Send/ReceiveNetworkDataEx() and NetworkErrorContinue(). It was way better than my own code.
I will test the new one and give you some feedback.

To get back to my problem, here is a new test : The client requests with a string, the server responds to this request with a string

- 14 connections + receivedata + deconnection : OK (each time there are 2 data events and receivenetworkdata returns -2 then the 3rd contains the data from the client ...