can put inside thread :(
it seemed that your server was writing data heavily while your client didn't receive duly.
@panjf2000 in that case, how can I prevent OOM while maintaining low latency(since this is extremely important for me)? is there a way in gnet to say discard or simply timeout after 5ms so I can prevent OOM? With ring buffer I thought I would never run into OOM. can you please share some light here
Hello guys, I`m having issues implementing the UDP protocol in gnet, maybe someone could help me ?
I open the connection, and Im trying to write it from my go routine inside of UDP server, then, Im expecting to read this information from other client from UDP server
The error I got is this: write udp 127.0.0.1:37666->127.0.0.1:9000: use of WriteTo with pre-connected connection
0
I assume that you are getting this error by calling the API of golang standard "net" API instead of gnet API？
But now, what I`m trying to do is listen all those events inside of func Ontrafic() from some external client reader, but for some reason I cannot listen to it.
I was using write function to send messages to clients connected, Any Ideas I would appreciate
I was using write function to send messages to clients connected, Any Ideas I would appreciate
one principle is that you should never be blocking in OnTraffic()
There is my main function where my server has started
I also add the gnetClient inside of my bigData struct, as you can see above
Now, there is my streaming function, where I will receive data from the callback trades, and also the I open a gnetClient UDP, and start to write to it
There is my server protocol, and also the results of OnTrafic, so there I can print every trade that got written by gnetClient inside of streaming function
And here is my simple external client, that I was expecting to Listen the events from the server 0.0.0.0:9000 / 127.0.0.1:9000
这个pool有什么用，没看出来可以提高什么性能？
@panjf2000
In the documentation, it describes two kinds of workflow:
- Multiple Reactors
- Multiple Reactors + GoRoutine Pool
How can I choose which workflow?
Is there any benefit to one or the other?
For the GoRoutine Pool, how can I specify pool size, etc. (the ant options)?
For context: I want to make a websocket re-broadcaster:
- Subscribe to 3-4 websocket streams
- Re-broadcast those streams to many clients (Each client can sub and unsub the streams they want)
