Skip to content

Commit 9eddb0b

Browse files
committed
update wording
1 parent 792c4a1 commit 9eddb0b

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

broadcasting.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ When the Redis broadcaster publishes an event, it will be published on the event
8686

8787
#### Socket.IO
8888

89-
If you are going to pair the Redis broadcaster with a Socket.IO server, you will need to include the Socket.IO JavaScript client library in your application's `head` HTML element. The Socket.IO serves this client for your convenience. Assuming you are running the server on the same domain on port 6001:
89+
If you are going to pair the Redis broadcaster with a Socket.IO server, you will need to include the Socket.IO JavaScript client library in your application's `head` HTML element. When the Socket.IO server is started, it will automatically expose the client JavaScript library at a standard URL. For example, if you are running the Socket.IO server on the same domain as your web application, you may access the client library like so:
9090

9191
<script src="//{{ Request::getHost() }}:6001/socket.io/socket.io.js"></script>
9292

@@ -99,8 +99,6 @@ Next, you will need to instantiate Echo with the `socket.io` connector and a `ho
9999
host: window.location.hostname + ':6001'
100100
});
101101

102-
You can run the server on de different domain, but be aware that Laravel session cookies will only be shared with the same domain, so you will need to user an alternative authentication method.
103-
104102
Finally, you will need to run a compatible Socket.IO server. Laravel does not include a Socket.IO server implementation; however, a community driven Socket.IO server is currently maintained at the [tlaverdure/laravel-echo-server](https://github.com/tlaverdure/laravel-echo-server) GitHub repository.
105103

106104
#### Queue Prerequisites

0 commit comments

Comments
 (0)