enqueue-dev: Don't use slashes in and prefix queue name with type in STOMP

I’ve been working with publishing to a STOMP queue and I’ve noticed that all my messages are prefixed with /queue/, which is going against my desired scheme for messages.

Looking at StompDestination, I see that both the prefix and the slashes are hard-coded.

It comes to mind that it probably shouldn’t be coded as such because everyone can and should be allowed to have their own conventions around how they namespace jobs (using.periods, maybe:colons, maybe/slashes, maybe\backslashes, etc…). Indeed, sometimes those conventions might be completely outside of their control! 😅

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 16 (14 by maintainers)

Most upvoted comments

Feel free to fork this repository https://github.com/php-enqueue/stomp

It’s a low priority project for me. So, dont expect much. I can review&merge PRs, do a release. That’s pretty much it.

We hardcoded them because of RabbitMQ. It needs it this way to properly route messages and that was the only broker we tested STOMP with.

I guess you use another broker. Which one?

The current values should stay there because of backward compatibility promise. Though, We should definitely add a way to configure them.

Another idea is to use scheme like this stomp+rabbitmq://, stom+activemq:// to switch to a property settings.