Speaking about chats, I am thinking about adding very easy chat example to the demo/tutorial page. I didn’t want to do it at the first place, as the stereotype of websockets is that they are only for chats 
There is another thing from my TODO list to resolve: how Drab should broadcast changes to the browsers. Drab has two version of DOM-modification commands: update and broadcast update. When you do:
def delete_button_clicked(socket, sender) do
bookid = sender["data"]["id"]
Books.Repo.delete(bookid)
socket |> delete("#book_row_#{bookid}")
end
it updates only the page in the browser from which request is sent - the browser where you click the button. But if other user have the same page opened, the row will persist until they refresh. Bad.
The solution for this is to broadcast such requests to all browsers which are currently viewing the page with the book list. In Drab, all DOM modification commands have the bang version. If we change the delete line to:
socket |> delete!("#book_row_#{bookid}")
it will update all the browsers viewing this page.
Currently Drab broadcasts such modifications to the viewers of the current page only. This is obviously not enough: the simplest example is when you are doing changes on page /users/1/books you probably want to propagate it to /users/2/books etc etc.
This is what I want to enhance in Drab. Broadcasts should be configurable! My first thoughts are to allow you to broadcast to:
:all:current_url- this is a default behaviour:current_controller- all browsers viewing the page rendered it the same controller, so/books/1,/books/2etc"topic"- use your own topic, like"books"- it would broadcast to all browsers which operates on the Commander listening to this topic
What do you think?
(me included 
)
