JSTLUV / ndt

Automatically exported from code.google.com/p/ndt
Other
0 stars 0 forks source link

Add java/flash plugin detection to JS UI page #154

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Page should detect if user has installed required plugin and automatically set 
proper backend for JS UI. Also user should be able to easily switch between 
flash/java NDT client.

Original issue reported on code.google.com by skost...@soldevelo.com on 1 Aug 2014 at 5:30

GoogleCodeExporter commented 9 years ago

Original comment by skost...@soldevelo.com on 1 Aug 2014 at 5:32

GoogleCodeExporter commented 9 years ago
Changes available on Issue154 branch (r1129). I have added two buttons allowing 
to set which client should be used as backend (java/flash). By default if java 
is installed then it is used. Feel free to review.

Original comment by skost...@soldevelo.com on 6 Aug 2014 at 5:23

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Does anyone have some feedback related to these changes? Will be very 
appreciated :)

Original comment by skost...@soldevelo.com on 25 Aug 2014 at 7:06

GoogleCodeExporter commented 9 years ago
Hey Sebastian!

We have a whole implementation ready. Sorry that I haven't posted the patch 
yet. Jordan (from OTI) did a great job on it. I will upload ASAP. Sorry for the 
delay!

Original comment by hawki...@measurementlab.net on 25 Aug 2014 at 5:47

GoogleCodeExporter commented 9 years ago
Hi Will,
what is the status of these changes? Would it be possible to upload them or/and 
list things that still need to be implemented to release new NDT version?

Original comment by skost...@soldevelo.com on 15 Sep 2014 at 9:40

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I attached patch from Jordan related to this issue. We should check how we can 
use it within our solution and merge both patches to trunk.

Short description of the patch:

"This patch adds a customizable feature for dealing with performance-limited 
flash
runtimes.  In a nutshell, the patch allows anyone who hosts an NDT
test to specify (via an HTML parameter) whether performance-limited
flash runtimes should (a) be treated the same as non-limited ones, (b)
only be allowed to run against a "fallback" server, or (c) not allowed
to run the NDT test via flash at all."

Original comment by jerem...@poczta.fm on 9 Oct 2014 at 12:12

Attachments:

GoogleCodeExporter commented 9 years ago
Sebastian, according to your question there is the following answer:

"The only open thing on an NDT release candidate out is getting it so that the 
Flash clients works out of the box when you do an RPM install (i.e. it’s not 
a weird arduous process of “edit this file, and that file, and install this, 
and then edit this file”. You just do a “yum install ndt-server”, start 
NDT, navigate to the NDT URL and it Just Works (tm))"

Original comment by jerem...@poczta.fm on 9 Oct 2014 at 12:15

GoogleCodeExporter commented 9 years ago

Original comment by jerem...@poczta.fm on 27 Oct 2014 at 10:44

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I have applied mentioned patch to Issue154 branch (also I have tested it and 
works OK). Does anyone have any feedback on these or/and my changes related 
client changing? If not, I will merge these changes into trunk. 

Original comment by skost...@soldevelo.com on 3 Nov 2014 at 3:34

GoogleCodeExporter commented 9 years ago
Both are fine by me

Original comment by AaronMat...@gmail.com on 4 Nov 2014 at 2:23

GoogleCodeExporter commented 9 years ago
Thanks for feedback. I have merged these changes into trunk.

Original comment by skost...@soldevelo.com on 4 Nov 2014 at 3:29