looking at the demo: synapse_daemon and synapse_clientYou mean like in a chat application? This is not implemented currently, though it shouldn't be too difficult to implement. I mean the messaging part, audio/video streaming is done usually via udp hole punching, much more difficult to implement.
imagining a scenario where synapse_daemon is active
and have 3 synapse_client connected on the server.
I couldn't understand how I could send message
from client1 to client2 or client 3
and I also could not understand how to send messages from any client to all clients
I'm a beginner so I'm asking is there any demo in this situation?Unfortunately no.
Sorry for my English I use google translator.No problem, I understood everything.
@datilasyes. chat application.
You mean like in a chat application? This is not implemented currently, though it shouldn't be too difficult to implement. I mean the messaging part, audio/video streaming is done usually via udp hole punching, much more difficult to implement.
yes. chat application.
in my situation it would be just text.
udp hole punching, much more difficult to implement.Well it is actually just a pair of sockets. It is a bit cumbersome, but it is not really difficult for you, although it IS difficult for beginners.
Well it is actually just a pair of sockets. It is a bit cumbersome, but it is not really difficult for you, although it IS difficult for beginners.In order to cover all the NAT traversal mechanism you have to do a lot of work in my opinion.
- added a new project(server_stress_test), server can be tested up to few thousand connections(requires 64 bit, see notes for more details)On a side note for high throughput/heavy load servers it is unwise to scale with threads. By default Linux only allows around 65k processes, which includes all threads of all programms running. If you spawn up a thread for each incomming connection with thousands of connections per second, you are going to take a substantial chunk of the PID space. Also threads are quite expensive, so it's not just that PID limit, but also the resources available.
a TimeOut property on the client would be very good for networks with high latency on the server and low connection on the clientThere is a ConnectionTimeout constant in unit uTCPSockets(default 5000 ms). Please increase it, then rebuild the client.
so we could control the connection timeout.