This repository has been archived by the owner on Feb 13, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 90
Question about Swoole and Container for parallel requests #632
Comments
Hi @yoh |
Hi @leocavalcante , thanks for the reply ! I use Siler v1.7.8 and Swoole v4.6.5
When I call my route one by one, it's OK :
When I launch wrk and call my route at the same time, it's not OK :
After wrk terminate, when I call my route, it's OK. I think using |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi @leocavalcante !
I'm happy with Siler on PHP-FPM and I try to use it with Swoole now :)
I have probably a silly question about the mix of Siler Swoole and the Siler Container :
Siler\Container
use singleton withstatic ::getInstance()
Siler\Swoole
useContainer\set|get
to store data about Routing/Request/ResponseWhen I add a counter with
Siler\Container\set('count', Siler\Container\get('count', 0) + 1)
, the count value is incremented requests after requests. I deduce from this behavior that the container values are shared between requests.When parallel requests income (req A and req B), are we sure that there is no conflict on
Container\get(SWOOLE_HTTP_REQUEST)
? I don't find doc about this on swoole website...How to store informations by request (logged user, config, etc.) and be sure there is no data leak between parallel (and/or one after the other) requests ?
Thanks !
The text was updated successfully, but these errors were encountered: