Production-ready, stable Kafka client for PHP
BREAKING CHANGE: Since version 4.0, the client no longer polls for network
events at shutdown (during object destructor). This behaviour didn't give
enough control to the user in case of server issue, and could cause the script
to hang while terminating.
Starting from 4.0, programs MUST call flush() before shutting down, otherwise some messages and callbacks may be lost.
BREAKING CHANGE: Since version 4.0, the client no longer polls for network
events at shutdown (during object destructor). This behaviour didn't give
enough control to the user in case of server issue, and could cause the script
to hang while terminating.
Starting from 4.0, programs MUST call flush() before shutting down, otherwise some messages and callbacks may be lost.
BREAKING CHANGE: Since version 4.0, the client no longer polls for network
events at shutdown (during object destructor). This behaviour didn't give
enough control to the user in case of server issue, and could cause the script
to hang while terminating.
Starting from 4.0, programs MUST call flush() before shutting down, otherwise some messages and callbacks may be lost.
BREAKING CHANGE: Since version 4.0, the client no longer polls for network events at shutdown (during object destructor). This behaviour didn't give enough control to the user in case of server issue, and could cause the script to hang while terminating.
Starting from 4.0, programs MUST call flush() before shutting down, otherwise some messages and callbacks may be lost.
BREAKING CHANGE: Since version 4.0, the client no longer polls for network events at shutdown (during object destructor). This behaviour didn't give enough control to the user in case of server issue, and could cause the script to hang while terminating.
Starting from 4.0, programs MUST call flush() before shutting down, otherwise some messages and callbacks may be lost.
WARNING BREAKS CONSUMERS: #324 , stick to php-rdkafka:4.0.0
for now
BREAKING CHANGE: Since version 4.0, the client no longer polls for network events at shutdown (during object destructor). This behaviour didn't give enough control to the user in case of server issue, and could cause the script to hang while terminating.
Starting from 4.0, programs MUST call flush() before shutting down, otherwise some messages and callbacks may be lost.
BREAKING CHANGE: Since version 4.0, the client longer polls for network events at shutdown (during object destructor). This behaviour didn't give enought control to the user in case of server issue, and could cause the script to hang while terminating.
Starting from this version, programs MUST now call flush() before shutting down, otherwise some messages and callbacks may be lost.
Fix build