You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got the basic websocket code (from the http://socketo.me/docs/push page) to work just fine, but I got completely confused when zeroMQ was added in. Is the pusher code meant to be IN ADDITION to the socket code that I have working for the basic client communication? Or does it replace it? Feels like it is in addition which means the socket app would still be run for client comm and the pusher would loop around to allow my back end PHP code to communicate with my users, triggered via various AJAX requests. Is that correct? I would need to start both of them before running anything in a browser?
It could be that the zeroMQ code supercedes the simple websocket code, can anyone shed some light on it so I can figure out how my back end code can initiate data pushes to desired clients/users?
The text was updated successfully, but these errors were encountered:
I got the basic websocket code (from the http://socketo.me/docs/push page) to work just fine, but I got completely confused when zeroMQ was added in. Is the pusher code meant to be IN ADDITION to the socket code that I have working for the basic client communication? Or does it replace it? Feels like it is in addition which means the socket app would still be run for client comm and the pusher would loop around to allow my back end PHP code to communicate with my users, triggered via various AJAX requests. Is that correct? I would need to start both of them before running anything in a browser?
It could be that the zeroMQ code supercedes the simple websocket code, can anyone shed some light on it so I can figure out how my back end code can initiate data pushes to desired clients/users?
The text was updated successfully, but these errors were encountered: