You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.. you shared a very good algo for connection-pooling, however i see that you used splQeueue instead of Swoole's Channel. I see splQueue is rich in terms of functions available on it.
In latest examples, we see Swoole Developers as using Channel for connection Pooling. So what is your say on it ? which is better ? and why ? OR, if you think both are better depending on certain context then can it be a good idea to give user an option to create a Connection Pool using splQueue where Channel is default parameter ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@twose
With reference to your older comment
on
post,
.. you shared a very good algo for connection-pooling, however i see that you used splQeueue instead of Swoole's Channel. I see splQueue is rich in terms of functions available on it.
In latest examples, we see Swoole Developers as using Channel for connection Pooling. So what is your say on it ? which is better ? and why ? OR, if you think both are better depending on certain context then can it be a good idea to give user an option to create a Connection Pool using splQueue where Channel is default parameter ?
Beta Was this translation helpful? Give feedback.
All reactions