laravel4cookbook

Real Time Chat 196
43
.
This was extracted from app/views/index/index.blade.php.
You’ll notice, apart from us using different field names; that we’ve change how the loop is done, the
class added to each “label” cell and how the input field is generated.
The reason for the change to the loop structure is simply so that you can see another way to
represented enumerable data in handlebars. Where previously we used a simple {{#each}} tag, we’re
now being more explicit about the data we want to iterate.
We add a special class on each “label” cell as we need to target these cells and change their contents,
in the event that a user decides to change their name.
Finally, we change how the input field is generated because we need to bind its value to the
IndexController’s command property. This format allows that succinctly.
.
You can learn more about Ember JS at: http://emberjs.com/.
Note On Nginx
For persistent sockets to remain open, Apache needs to keep a single process thread occupied. This
is a problem as it will consume vast amounts of RAM over a shorter time period than non-persistent
connections would. For this reason; I highly recommend using either Nginx or an event-based
language to create your chat application.
It’s not that Apache sucks; this is just not the sort of thing it was designed for. Nginx, on the other
hand, is event-based and doesn’t hold onto a whole thread while it waits for activity through the
open socket.
.
You can learn more about Nginx at: http://wiki.nginx.org/Main.