v0.7.0

[TuanKiri]

What's Changed

• Functional options by @TuanKiri in Functional options #8

Full Changelog: v0.6.0...v0.7.0

---

This discussion was created from the release v0.7.0.

[peakedshout]

Hey, I'm curious who paid attention to the outdated socks library I wrote, obviously this kind of library is not very technical, and I was surprised that there was a collection? So I'm going to take a look at what you're doing, and it's surprising that you're actually learning and trying to write your own arsenal. But I'm telling you very clearly that my arsenal is outdated, and I haven't uploaded my latest designs (maybe forever). But I'm curious if you've found my implementation bug, and I took a cursory look at your code and found that there was a concurrency problem. If you just write casually, then please ignore my say.

[peakedshout]

No, don't put expectations on the client, that's very bad, because the server is trying to serve as many clients as possible, not the message. In your follow-up logic, bind a UDP port based on a message, do you think that in a short period of time, explosive concurrency can apply for tens of thousands of UDP ports?

[peakedshout]

Then, UDP proxy is not a simple request to send and receive, not all scenarios are DNS requests, please read more specification documents. There is nothing wrong with simple design, but design that does not provide solutions for complex scenarios is worthless, and although it is rarely used, since it is provided, it should be perfected basically.

[TuanKiri]

I'm running tests on qBittorrent. It makes requests to udp trackers and sends a large number of datagrams from different ports. If the messages are processed sequentially, nothing works. If in parallel, everything works. You are correct in your reasoning. I am new to network programming and am trying to learn it

[peakedshout]

Obviously you don't understand the concept of sesion, it's a concept at the user level, it's not a question of parallel or serial processing of messages, but you don't have a proper processing logic, don't consider resource overhead and controllable expectations, it's very bad.
It looks like my advice is invalid here, and maybe you'll only find the problem when you hit a bottleneck. I've been using the translator and this communication makes me tired, so be it, good luck.
Regarding the use case of UDP, I would like to mention a very common one: http3, you should understand how it is done at the network layer.

[TuanKiri]

Thanks a lot for your time! I really appreciate it.