search

hazymayon / bigbluebutton

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

Hide access to debug console (0.64?) #404

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
- turn off/hide debug console access. this could be done at create() or
join() as boolean parameter for dynamic conferences.

Original issue reported on code.google.com by goike...@gmail.com on 12 Mar 2010 at 5:41

GoogleCodeExporter commented 8 years ago 
I agree with the need to hide the access to the debug console.  But, this 
should be a 
server-setting, not an API parameter....  Or, you could have BigBlueButton.html 
and an 
alternate BigBlueButton-debug.html - if you wanted to debug on a production 
server, 
you could manually go to the debug version

we just need to avoid adding a ton of parameters to the API - every parameter 
you add 
creates another order of magnitude of possible combos / needed testing / 
complexity 
that will break.

Original comment by jeremyth...@gmail.com on 12 Mar 2010 at 2:51

GoogleCodeExporter commented 8 years ago 
The debug window needs to be separated from the main and refactored a bit. It 
should be 
removed all together when compiling a non-debug version, partly to make the 
client 
smaller. See Issue 400 for more info

Original comment by Me.S...@gmail.com on 12 Mar 2010 at 2:55

GoogleCodeExporter commented 8 years ago 
Server side is fine, either way. I do think being able to debug a production 
server
w/o recompiling is advantageous.

Original comment by goike...@gmail.com on 13 Mar 2010 at 1:02

GoogleCodeExporter commented 8 years ago

Original comment by Me.S...@gmail.com on 29 Sep 2010 at 2:15