Calling request body close in the item handler (see: https://groups.google.com/d/topic/golang-nuts/K9e0tyfU2hY/discussion)
Started adding web socket support to the server following the example at http://gary.beagledreams.com/page/go-websocket-chat.html
Send out message objects with view models to the browser instead of string messages
Include the view.Model type into repository items, so the server can send the view model out to the browser when an item changes
Renamed the path provider file
Added a function for opening urls in the browser. This function is not yet integrated. I have taken the function from https://github.com/advincze/golang-websocket-flot/blob/master/src/srv/main.go
Formated the wsHandler code
Working on route-specific web socket update-connections
Fixed a bug related to lop-level items paths
Strip the leading slash from item routes when establishing a web socket connection
Send updates only to those sockets which have been created for that specific route
Reduced the size of the message channel. There is no need to make room for 256 messages
Got the web socket content update working for documents
Websocket updates for collections and repositories
Attach a change handler to the root of each item index
Refactored the themes package
Removed the item index watcher again because it is causing problems
Moved the autoaupdate javascript from the master template to the theme
Make sure the current route is decoded before comparing it with the route sent over the socket connection
Introduced a level attribute for all items starting at zero