From 84484f6603ad82c044a97649e0c9a9141b545bf1 Mon Sep 17 00:00:00 2001 From: Chris Boden Date: Mon, 21 Nov 2011 10:51:28 -0500 Subject: [PATCH] Docs Updated details in readme --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 435d819..f9d0e8e 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ #Ratchet -A PHP 5.3 (PSR-0 compliant) application for serving and consuming sockets. +A PHP 5.3 (PSR-0 compliant) component library for serving/consuming sockets and building socket based applications. Build up your application (like Lego!) through simple interfaces using the decorator and command patterns. Re-use your application without changing any of its code just by wrapping it in a different protocol. @@ -15,8 +15,8 @@ Shell access is required and a dedicated (virtual) machine with root access is r 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. -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. +Cookies from your domain 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 web and socket servers. 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.