search

joekain / phobs

(Ph)oenix (obs)erver
MIT License
0 stars 2 forks source link

Decide organization of channel data #2

Open joekain opened 9 years ago

joekain commented 9 years ago

My thoughts so far was to have multiple topics on the channel. So for example, the top level tabs of observer "System", "Processes", "Memory Allocators" could be different topics. A client could join a new topic as the user switches tabs. Server would only generate and broadcast data if there are clients subscribed to a given topic.

With the above organization there would be "Load Charts" and "Applications" which would need d3. Should server send JSON that can feed into d3? Or should it send raw data and client sets up d3?

In the "Processes" tab we should be able to click on a specific process and bring up details. If, for example, we click on process with PID <0.22.0> then I wonder if we could dynamically create channel topic "phobs:proc:0.22.0" and broadcast the relevant data for it.

joekain commented 9 years ago

cc @dgoldie

dgoldie commented 9 years ago

@joekain hmmm, first thought is I didn't get an email about this... Json: I thought Channels is doing that for us already?? dynamic topics: cool idea !! definitely should try that. Though, I'm not sure its necessary here. I'm going to work on getting the basic data stream you have into d3.

joekain commented 9 years ago

@dgoldie,

hmmm, first thought is I didn't get an email about this..

Hmm, that is strange.

Json: I thought Channels is doing that for us already??

I guess that's true. Can you structure it to match what D3 wants?

dynamic topics: cool idea !! definitely should try that.

Ok, I've been working on reporting the system data (from :observer system tab) and then I want to try writing the HTML/CSS/JS to add tabs to the app. After that I'll look at adding support to try dynamic channels out for the process information.