Mike Samuel
Mike Samuel
I answered your questions on the cache, and did all the remaining TODOs. If the cache is a concern, I could try benchmarking with and without. If that sounds useful,...
I rebased around releases 2.3.{0,1} which required a `git push -f`. That required one manual merge around the new 'triple question marks are ignored' and a test I added in...
@dougwilson If this is effectively dead, please let me know and I'll close out the PR.
Thanks for giving it a read. > attacks based on the intersection of Crypto and Compression I'm afraid I'm unfamiliar with the specifics of Node.js that make it particularly vulnerable...
> Node.js generally has very few protections built-in to prevent a malicious party from consuming significant resources. Maybe it's worth noting this when contrasting client- and server-side JS. Something like...
It seems like there might be a lot of problems of the form: 1. An HTTP request handler acquires some resources 2. Some promises are completed, some are not ......
It seems like, if the rate is low, then you've got a slow leak, but might be ok if you have a baby sitter. If the rate suddenly spikes, that's...
Sounds good. What can I do to help?