Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[Messenger] [FrameworkBundle] Added `semaphore` transport. #34413
The Semaphore Transport allows you to send and receive messages on System V message queues. The
# .env MESSENGER_TRANSPORT_DSN=semaphore://%kernel.project_dir%/.env # Full DSN Example MESSENGER_TRANSPORT_DSN=semaphore://%kernel.project_dir%/.env?project=M&message_type=1&message_max_size=1024
A number of options can be configured via the DSN or via the options key under the transport in messenger.yaml:
ogizanagi left a comment •
So I gave it a try on an existing project. It seems to work great so far.
However, about using
* Fixed too much indent. * Removed `PlatformUtil` internal class. * Used method `extension_loaded(sysvmsg)` instead `PlatformUtil::isWindows()`.
Thank you for this PR. I see that you done a great job with this, and this transport looks really good.
However, I am strongly against adding new transports. Symfony should only provide transports that are use by the vast majority of people. AMQP, Redis, Doctrine, and custom transports like
I know there are special and super cool transports, but I believe that they should not live inside of Symfony organisation.
I vote for closing this PR. And I strongly recommend @CedrickOka to create a library of this great code so other can enjoy this semaphore transport.
For the record:
The PR will be merged if Semaphore is considered a popular transport.