Roadmap?

Some things have happened lately. Firefox 4 beta supports WebSockets. [LiveReload](http://github.com/mockko/livereload) pops out and its server is using WebSockets. As I see it, next reasonable steps would be:
- WebSockets-based XRefresh for Firefox
- The same file monitoring server for XRefresh and LiveReload

Current response format of LiveReload is just a filename string, like `main.css` or `index.html`. I think we should send full path, like `/Users/nikitavasilev/Sites/tmp/test.html`. Some benefits:
1. The filename doesn't work well when few CSS/JS-files named the same. For instance, `foo/main.css` and `bar/main.css`.
2. A full path will allow as to do a "[strict mode](http://github.com/darwin/xrefresh/issues#issue/9)" when we edit something on `file://` scheme.

darwin, how hard would be to port XRefresh to WebSockets?
LiveReload developers ([andreyvit](http://github.com/andreyvit) and [dottedmag](http://github.com/dottedmag)), what do you think about the same server?