Christian Lück

Thanks for these interesting links! - stat cache garbage collection: Not used by ReactPHP and I don't really see this happen any time soon. Running this in an unpredictable timer...

@kelunik I still think you're making a valid point here. The current behavior has been implemented >5 years ago which means that this is how this component has always worked...

I'm currently looking into updating #218 and I agree that this can be used to avoid this issue. However, this will only limit the number of concurrent requests and thus...

Not sure if that's reasonable, but you're raising a valid point! Arguably, we're discussing a premature optimization here, so I would suggest getting #218 in first and then look into...

> my motivation is to benefit from the existing Resolver-Factory and also have access to the underlying executor, in detail to the `query` function. in the current implementation there is...

> just expose an function like `createExecuter` for internal and external use in the Factory-Class? Sounds about right, but just an idea at this point and we'd have to take...

Makes perfect sense! I understand where they're coming from, but I agree that they feel more like a burden than actually helping with implementing new features in the current state...

The main focus is currently on getting the v1.0.0 out. As such, there are currently no immediate plans to build this from our end (no demand at the moment), but...

@cordoval Yes, there are a number of use cases where you can use this project without requiring HTTP/2.0. For example, if you're using this project behind a reverse proxy (such...

@valzargaming I can definitely see us implementing HTTP/3 in the future, but baby steps first! In the meantime, using a reverse proxy to handle HTTP/2 and HTTP/3 is perfectly reasonable...