On Mon, 2002-03-25 at 22:13, Andrew Bennetts wrote:
On Mon, Mar 25, 2002 at 09:55:01PM -0600, Glyph Lefkowitz wrote:
Thanks for trying this out and giving feedback!
I'm thinking I can find some good uses for it at work. It is currently geared towards configuration (and that's something I've got alot of use for), but what I think I have the most immediate use for is status reporting -- statistics like "served n requests", "been running since", "last packet from upstream data feed arrived at ... and had a timestamp of ...".
It originally seemed to me that data-display would be a different component. (Remember Sean's twisted.metrics, anyone?) I guess you're right that it would be handy to display it in the same web interface, though... hmm...
The sort of configuration I'd want to do is basically what you appear to already have -- start component X listening on port 1234, and connect it to upstream server Y on 9876. I possibly also want to save configuration to the registry rather than to taps, but I think taps are a better idea.
You can introspect on the objects to save them to wherever :-). I'm sure that the registry can be contorted in order to save "arbitrary" Python objects.
Say, is there anyway to do "offline" editing of the configuration held in a tap?
Well, the existing coil code can edit "offline" as well as "online" configurations; it just takes an Application object and mutates it. Adding some buttons to the interface to save / load the app to a particular file should be trivial.