Skip to content
This repository was archived by the owner on Oct 22, 2019. It is now read-only.

Conversation

@rdohms
Copy link
Contributor

@rdohms rdohms commented Oct 9, 2018

When using predis extension, the underlying library will re-use
connections to same host/port in case of persistent connections. This
becomes an issue when the user's application uses the same host of Redis
but has different databases, meaning that this library will write to
whichever database is previously used by other parts of the code.

Using a persistent id forces the library to create a new connection
that will not conflict with any other connections being used by the
application.

When using `predis` extension, the underlying library will re-use
connections to same host/port in case of persistent connections. This
becomes an issue when the user's application uses the same host of Redis
but has different databases, meaning that this library will write to
whichever database is previously used by other parts of the code.

Using a persistent id forces the library to create a new connection
that will not conflict with any other connections being used by the
application.
@rdohms rdohms mentioned this pull request Oct 14, 2018
@NoelDavies
Copy link

This project is dead, but I'm maintaining it under my employer - https://github.com/endclothing/prometheus_client_php. Feel free to submit the PR there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants