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
{{ message }}
This repository has been archived by the owner on May 25, 2018. It is now read-only.
I want to take some data on server side (RoR with faye-rails) from client side (Ruby + faye client). The problem is that the client is behind a firewall and because of it, I connecting client to server and wait for any command from it. Client can publish back to channel all requested data but I can't understand how I can take back this message in the server controller after publishing request to client channel.
This is the controller action:
def send_request
require 'net/http'
publication = ClientController.publish("/client", params[:query])
publication.callback do
@res "[PUBLISH SUCCEEDED]"
end
publication.errback do |error|
@res = "[PUBLISH FAILED] #{error.inspect}"
end
end
How I can take a response from client in the usual controller?
Thanks a lot.
The text was updated successfully, but these errors were encountered:
I made it with faye-websocket. Ruby clients (with dynamic IP) connects to my Rails middleware faye-websocket server. When I need information from any client I call the method from middleware and wait N seconds for response from client through websocket.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
I want to take some data on server side (RoR with faye-rails) from client side (Ruby + faye client). The problem is that the client is behind a firewall and because of it, I connecting client to server and wait for any command from it. Client can publish back to channel all requested data but I can't understand how I can take back this message in the server controller after publishing request to client channel.
This is the controller action:
How I can take a response from client in the usual controller?
Thanks a lot.
The text was updated successfully, but these errors were encountered: