PARSE clocks.

[Hal Murray]

verm at darkbeer.org said:
> What essentially happens is your browser opens a socket to the webserver.
> From  there it streams JSON which your browser renders.  This is a *lot*
> faster as the  server has to do zero rendering it's literally internal data
> structures -> JSON  -> socket.  which is extremely fast.

> Buildbot doesn't scale well this was the solution to help it do just that.
> It  also avoids constant refreshes on the server which requires more
> rendering. 

That all makes sense, but I'm a bit surprised that I seem to be the first one 
to notice that what I thought was a major browser from a major distro doesn't 
work with that setup.

It doesn't surprise me much that there is a problem, but it does surprise me 
that there isn't a FAQ type entry with a recipe for making it work and/or 
that there isn't already a command line tool to display the status.

Any ideas why it isn't working better than blank-screen?

What browser/OS are you using?  Others?

Just to make sure we are on the same wavelength...  I haven't seen anything 
from http://buildbot.ntpsec.org but a blank screen.  Are there any URLs that 
show something/anything without websockets?

I double checked.  I can't find the flag to enable/disable websockets.  I'd 
guess that means they gave up on disabling it.  (But that seems weird since I 
found a note about that being a handy way to avoid some security problems.)

I tried netstat -t after loading https://buildbot.ntpsec.org/
I didn't see anything interesting - no dangling sockets.

Is websockets a wild goose chase?

What socket do I get the JSON on?  Do I have to send anything to get it 
started, or can I get something useful with netcat? (or some other tool)






-- 
These are my opinions.  I hate spam.