I tied myself to nodes, being new for both STOMP and 0MQ, but in a nutshell I want to facilitate the interaction of the client with the client in the browser with interaction with PHP MOM or several PHP MOM. I consider using WebSocket to provide constant two-way connections (when available) between html5 browser clients and MOM endpoints, and then use these endpoints to facilitate communication between any number of browser clients that can be connected 1-1, 1- many, many -1 relationship.
MOM endpoints can interact with other servers or with each other for different purposes, and I believe that 0MQ can be a viable way to quickly exchange information between these servers. Like a messaging protocol between clients, STOMP looks good (although I know some problems with protocol definition) ....
.... so here is my point of embarrassment. In order to use STOMP, MOM had to be a STOMP broker, and if it is a STOMP broker, as 0MQ is a “brokerage” level of messaging, do I not defeat the purpose of using both?
To clarify, I am considering 0MQ for MOM-MOM communications and STOMP for client-client communications.
Unless, of course, there is a way by which you could reassign 0MQ to facilitate the interaction of the client with the client? I think my real mess with 0MQ is an easy messaging layer of messages, not a protocol or both? If only its layer, I can not use 0MQ to transport STOMP messages?
If anyone could shed light on 0MQ for me, I would be very grateful - thanks!
source
share