Hi Kelly,
> Assuming the app always attempts communication with registered listeners,
> and then must timeout and unregister a dead listener...at that point
> aren't we just at my preferred solution: socket communication?
I don't know much about sockets, so I couldn't say. If the console
will con
Kelly,
> The most appealing method (in my mind) is to develop a socket protocol
> that allows the application to communicate with the console. The drawback
> here seems to be that the console will not usually be active, and I'm
> concerned that attempting to establish a connection will impose too
I'm developing a web-based framework ("the application") and would like to
implement an ncurses-based realtime monitoring facility ("the console").
The application currently writes events to a database history table, but I
don't think having a console that constantly requeries that table would be
3 matches
Mail list logo
