Carlos Fuentes
Carlos Fuentes
I'll check them out
I've been playing around with this recently, and I believe that is not an easy task given the little context we know when instantiating a plain text connection. There's no...
>Whenever a commit lands on main I'd like to suggest to not to this, in my experience, this usually doesn't end well. >Action workflow_dispatch to land a semver-patch release, reverting...
Default is 10mb, no customizable; so I'm imagining cutomize it with a lower upper bound? or what do you have in mind exactly?
Currently not without an overhead. Basically Piscina threads are meant to be destroyed if idle. This happens immediately by default, and can be extended accordingly. Sadly, even passing `Inifinity` won’t...
> Hey! I would like to take a shot at this. Any recommendations on where to start? Of course! I'd start by looking at the `idleTimeout` Piscina supports that states...
>The only drawback I can think of right now is that all of the workers created by the threadpool will be long lived, but I think that the expected behavior...
> Without consuming the body I couldn't get node to gc the Response returned from fetch And that happens due to WebStreams or also with normal Streams?
It might be worth it to also extend documentation with advice to be mindful sensitive data, just for overall awareness while caching. Especially as headers should not be used for...
That's a blur line between sensitive and security information; tho I was referring to response headers in specific.