-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple clients #48
Comments
Hello @appleshine,
delegate: YOUR-CUSTOM-DELEGATEPlease keep me inform about multiple client issue :) |
I created my own delegate extending from StompClientLibDelegate socketClient.openSocketWithURLRequest(request: url, delegate: myDelegate) the websocket is connecting properly and the topic is being subscribed. but for some reason I cant get any response from the subscribed topic.
this method is not going through, if i set the delegate back to self. i can receive the message with no problem. both the classes have the same delegate functions and code tho |
@appleshine Can you share the example project with me? We can make it faster in this way. Also please tell me which version of the library do you use? |
Unfortunately I do not have an example project. My websocket url is localhost :( But my delegate is as below:
in my main view controller
|
Hey @appleshine, Also, I have a little question for you. Why do you need to use multiclient? You can access more than one topic with just one client? Please describe your use-case maybe you're just trying a hard method to solve it :) |
Theres no error but I receive no response/message from the server.
I understand that I can subscribe to multiple topics, but in my case, the websocket servers are created on multiple VMs thats why I have multiple urls for me to connect to. |
@appleshine Can you provide me with an example server-side project for me? I would like to help you :) |
Hi, is it possible to have multiple StompClientLib clients that connect to different URL? How can the delegate differentiate the clients?
Thanks in advance!
The text was updated successfully, but these errors were encountered: