still integrating with aiohttp?
I have scratch through the code and find the aiohttp is only used in resolver.py, judge.py and providers.py among the library.
And I'm curious the progress of replacing the Server.serve portion from socket to http/https via aiohttp? Is it aiohttp doesn't support socks that prevent you to use low-level api rather than high-level api?
Thank you for your question and attention to the project!
Actually, the decision on the final implementation of the serve function is pending. Possible in the future the serve function will be implemented by using aiohttp, it is also possible that the whole project will be refactored with raw sockets instead of aiohttp (not sure if it makes sense?). And yes, aiohttp doesn't support SOCKS, so serve function implemented using low-level api.
You might also look at PySocks for this if you haven't already. It works well in other projects of mine.
Probably more relevant, there is aiosocks now for handling SOCKS.