> On 27 Jul 2022, at 17:16, Morten W. Petersen <morp...@gmail.com> wrote: > > Hi. > > I'd like to share with you a recent project, which is a simple TCP proxy > that can stand in front of a TCP server of some sort, queueing requests and > then allowing n number of connections to pass through at a time: > > https://github.com/morphex/stp > > I'll be developing it further, but the the files committed in this tree > seem to be stable: > > https://github.com/morphex/stp/tree/9910ca8c80e9d150222b680a4967e53f0457b465 > > I just bombed that code with 700+ requests almost simultaneously, and STP > handled it well.
What is the problem that this solves? Why not just increase the allowed size of the socket listen backlog if you just want to handle bursts of traffic. I do not think of this as a proxy, rather a tunnel. And the tunnel is a lot more expensive the having kernel keep the connection in the listen socket backlog. I work on a web proxy written on python that handles huge load and using backlog of the bursts. It’s async using twisted as threads are not practice at scale. Barry > > Regards, > > Morten > > -- > I am https://leavingnorway.info > Videos at https://www.youtube.com/user/TheBlogologue > Twittering at http://twitter.com/blogologue > Blogging at http://blogologue.com > Playing music at https://soundcloud.com/morten-w-petersen > Also playing music and podcasting here: > http://www.mixcloud.com/morten-w-petersen/ > On Google+ here https://plus.google.com/107781930037068750156 > On Instagram at https://instagram.com/morphexx/ > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
