Rob Landers
Rob Landers
> I would be glad if this conclusion turns out to be wrong, but it’s something to keep in mind. I did a bit of research back in the Fiber...
> have you ever encountered something similar? No because I use docker images + composer for upgrades/installs/etc.
@firecow this is almost always an issue with something in C corrupting memory due to doing something non-thread-safe (or something else, but that's the most common one). In the issue...
@dunglas it would have to halt all PHP processing in-general. There's no locks around opcache reads (there are on writes though), so the proper fix is to add rw-locks to...
I think there is a lot to do on the PHP side. For example, allowing function callbacks + state + objects to pass the thread boundary (TSRM makes these things...
> If you mean running the actual handler inside coroutine This is what I was referring to. If we were to throw these things onto a go routine, go may...
We'd probably need https://github.com/php/php-src/pull/16565 as well, so we don't need an exclusive lock to read shared state.
> Yes, that can be done, but SuperGlobals have the drawback of lacking immutability. That’s why request and response objects are the most correct approach, since they immediately localize memory...
The fact that superglobals are not disregarded in FrankenPHP is one of the reasons I even contributed in the first place. You may feel they are a "mistake" in the...
I believe this is due to bypassing filters? I can't remember, but I'll check when I rebase #1658