Decouple Websocket code from HTML front end

[nkinkade]

The change set in this PR is intended to do a little better job of not making assumptions about the HTML front-end in the back-end javascript code. The goal is to allow anyone to reuse the back-end code mostly unaltered (perhaps as a git submodule) while having relative freedom to control the user interface. One specific use case for these changes will be on the M-Lab website (www.measurementlab.net), where a bit more stylistic control is needed for the UI. One non goal of this PR is that anything should change about the current behavior of the backed test or UI when run via fakewww in any deployment.

[aaronmbr]

This looks good. Thanks! A few minor comments, would it make sense to pass a URL around instead of just the hostname/port/protocol/path? Also, there are some "typeof == undefined" checks, would it make sense to ensure those variables always exist with some sane defaults?

Cheers, Aaron

[nkinkade]

Hi, Aaron. Sorry I missed your comments. Even though the PR is merged and closed, I wanted to address them for the sake of history.

• You're right that it might be easier to just pass an entire URL instead of a bunch of parameters that comprise a URL, and then worrying about reconstructing it later. This can be an improvement for v2 of these changes.
• The reason I added those "typeof == undefined" checks is that the fakewww UI set those variable for reasons I wasn't sure of, so I didn't want to touch them, presuming that you had some purpose in adding them. But we don't set those in the M-Lab UI, so rather than discarding them from the code, which could have possibly broken the fakewww interface (or somebody else's interface), I just wrapped them. The idea was to be sure that no changes in this PR would affect the existing, unmodified behavior of the WS frontend in the NDT repo.

Thanks!

Nathan