is there any way to specify that server-side never times out in Racket web server?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
is there any way to specify that server-side never times out in Racket web server?
What if you specify a timeout of
0?If that’s not an option or doesn’t work you can set the timeout for some unreasonably large number such as
31536000– the number of seconds in a year, or 30 days, or whatever is going to be more long lived than the server is likely to be in your case.That being said, it would be very strange to have a timeout that’s either effectively or actually infinite. At some point, all servers generally need to give up and assume the client is never coming back. It’s the healthy thing to do. Otherwise the server will just sit there sad, dejected, quietly logging, “Why didn’t they ever come back?! Did I not serve their needs adequately? I live only to serve – it is in my name!”
…on on a more serious note, it can lead to what looks like a memory leak when you have open connections with no timeout just sitting out there, slowly accumulating resources (memory) over time. In many such cases you have to restart the server app to get those resources released.