On 06 Dec (16:52:45), Karsten Loesing wrote: > Hi everyone, [snip] > One important and still somewhat low-hanging fruit is: #10 give > external developers more support when developing visualizations that > could later be added to Metrics. This requires better documentation, > but it also requires making it easier to install Tor Metrics locally > and test new additions before submitting them. The latter is a good > goal, but we're not there yet. The documentation part doesn't seem > crazy though. David, if you don't mind being the guinea pig yet once > more, I'd want to try this out with your latest visualizations. This > is pending on the JavaScript decision though. The current viz. I have are all generated by a Munin server which every 5 minutes collect data points on the "munin node" and generates graph (PNG). So as a client accessing the server, you only have to fetch a PNG, all the CPU work for the graph is done on the server side. It's indeed the JS vs non JS discussion where you basically want to put the load on the client side instead of the server. Please expand on the what would be required of me for this guinea pig experiment? :) Thanks! David
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev