faeez/mxmbsocket
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Repo. Project Releases Wiki Activity

readme

Browse Source
This commit is contained in:
Chris Boden 2011-11-15 08:57:20 -05:00
parent 2720864d79
commit 9d36a37bf5
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -11,13 +11,13 @@ Re-use your application without changing any of its code just by wrapping it in
##Requirements ##Requirements
Shell access is required and a dedicated (virtual) machine with root access is recommended. Shell access is required and a dedicated (virtual) machine with root access is recommended.
To avoid proxy/firewall blockage it's recommended WebSockets are run on port 80, which requires root access. To avoid proxy/firewall blockage it's recommended WebSockets are run on port 80, which requires root access.
Note that you can not run two applications (Apache and Ratchet) on the same port, thus the requirement for a separate machine. Note that you can not run two applications (Apache and Ratchet) on the same port, thus the requirement for a separate machine.
Cookies from your Apache/Nginx/IIS server will be passed to the socket server, allowing you to identify users. Cookies from your Apache/Nginx/IIS server will be passed to the socket server, allowing you to identify users.
It's recommended using a database/cache solution to store session data, so it's accessible on both servers. It's recommended using a database/cache solution to store session data, so it's accessible on both servers.
I demonstration of this will be posted (eventually). A demonstration of this will be posted (eventually).
See https://github.com/cboden/socket-demos for some out-of-the-box working demos using Ratchet. See https://github.com/cboden/socket-demos for some out-of-the-box working demos using Ratchet.