multiple servers one script

[gad2103]

It would be awesome if this could listen to several servers running on different ports. That way events from different servers could trigger changes. Any ideas on how to do this?

[andreyvit]

Well my plan is for the next version of LiveReload protocol to support relaying messages, so that after one server starts listening on the port, other servers will be able to connect and talk to the connected browsers.

I think that it makes sense for the browser side to stay as simple as possible and only connect to a single server.

[gad2103]

I see your point but it would be nice for the client to be able to pass in
an options object with a list of ports. My use case is not uncommon:
wanting to run separate watch tasks through grunt that are completely
independent of each other but still want to reload the browser. Each watch
task can be configured to run on a different port and relay messages to one
script in the client....
On Jan 31, 2015 11:13 AM, "Andrey Tarantsov" [email protected]
wrote:

Well my plan is for the next version of LiveReload protocol to support
relaying messages, so that after one server starts listening on the port,
other servers will be able to connect and talk to the connected browsers.

I think that it makes sense for the browser side to stay as simple as
possible and only connect to a single server.

—
Reply to this email directly or view it on GitHub
#30 (comment)
.

[andreyvit]

Is there a reason why this use case is not covered by what I have described?

[pbedat]

I think relaying is a great idea @andreyvit! Do you already have it on the roadmap?