NDT-DEV email list created

[Peter Boothe <>]

MLab is very excited about websockets and the _javascript_-only network tests that they enable, so if we can get websocket support merged into mainline NDT sooner rather than later that would be great.  We have found that, for an increasing number of users, Flash and Applets are no longer an acceptable solution - applets now cause horrendous security warnings and flash is disabled on an increasingly large number of platforms.  This leaves us a bit in the lurch in terms of how to get measurements from people running a web-browser until we get websocket support on the NDT server.

Also on the positive side, the websockets branch is fully unit-tested and end-to-end tested ('make check' should run the tests on your local machine), and it looks like it can be merged with no conflicts.

  -Peter

On Fri, Apr 10, 2015 at 6:36 AM, Sebastian Kostuch <> wrote:

Hi all,
it has been long time since last NDT final release and also preparations for this one are taking few months so far. Isn't then better approach to release new NDT 3.7.0 final version ASAP with minimal changes/fixes required to do so and after that within few following months make new release (3.7.1?) which would contain new features (websockets + there are also changes on MultiplePorts branch which would be good to integrate with it as well) ? Merging websockets now will probably make release process last longer so what do you think about such approach?

Kind regards
Sebastian

On 09.04.2015 22:54, Nathan Kinkade wrote:

Aaron,

I really like this plan.  I think that by the time RC4 is out we'll
have a pretty good _javascript_ Websockets client assembled.  It's
already functional, but we just need to make it a bit more robust when
it comes to error handling, and apply some general stylistic changes.
And as you say, it is much easier to do minor version updates than
some new release for a different feature.

Thanks,

Nathan

On Thu, Apr 9, 2015 at 3:04 PM, Aaron Brown <> wrote:

Hey Jordan,

Given the performance … eccentricities that have been encountered, we’ll need to do another -rc with some changes to the warning message (along with having it use the flash applet’s definition of ‘good environment’). Given that the WebSockets branch has been stable, my thought is that we could merge that in for -rc4. Then when we do work some more work on the websocket client, it’s just a minor release to update the client instead of the whole websocket environment too. What do others think?

Cheers,
Aaron

--

Peter Boothe |  | ᴹ̶LAB | http://measurementlab.net