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
Internally, the RedisClient would work similar to what is currently called a "lazy" client, but we'll probably get rid of this wording altogether. This means it would automatically create the underlying connection to Redis only when it's actually needed and will close this connection after a short while when it is not in use anymore. What is currently called "idle" time would probably be reworded to be more of a "keepalive" with much lower defaults.
Additionally, we'll probably fire "open" and "close" events as needed (loosely inspired by https://github.com/clue/reactphp-eventsource). Unlike the current version, my idea is to also keep the instance in a usable state even after calling close() on it. Reusing the same instance at a later time makes a lot more sense in long-running applications instead of locking it in an unusable state.
This is obviously a BC break, but there are no plans to break any of the existing code besides this. Most consumers should be able to upgrade to the new instantiation without issues, actual query APIs etc. would not be affected.
There are plans to simplify the API by removing the
Factory
and instead replacing it with a simplerRedisClient
constructor. In other words, this:Could potentially look like this:
Internally, the
RedisClient
would work similar to what is currently called a "lazy" client, but we'll probably get rid of this wording altogether. This means it would automatically create the underlying connection to Redis only when it's actually needed and will close this connection after a short while when it is not in use anymore. What is currently called "idle" time would probably be reworded to be more of a "keepalive" with much lower defaults.Additionally, we'll probably fire "open" and "close" events as needed (loosely inspired by https://github.com/clue/reactphp-eventsource). Unlike the current version, my idea is to also keep the instance in a usable state even after calling
close()
on it. Reusing the same instance at a later time makes a lot more sense in long-running applications instead of locking it in an unusable state.This is obviously a BC break, but there are no plans to break any of the existing code besides this. Most consumers should be able to upgrade to the new instantiation without issues, actual query APIs etc. would not be affected.
The same API discussion also applies to SQLite (clue/reactphp-sqlite#47), MySQL (friends-of-reactphp/mysql#147) and others
Builds on top of #114
The text was updated successfully, but these errors were encountered: