Alex Sergeyev
Alex Sergeyev
Anyone else wants this? Problem is that subscribing to stderr and stdout on two different sockets requires coordination :( So when you subscribe to output you should specifically request "same...
NEUTRAL leaning towards DROP... just because not everything I need in quick and dirty way needs to be implemented as websocket and it's a good complimentary thing to have. But...
Conditional compiling is not useful for most software. Maintaining code is still a necessity. Disabling feature by not using it is as good.
for me personally it's more important to see if this particular tool (websocketd) is good place to have CGI - serving as a feature. There is really not much to...
@joewalnes I wonder if you need that really or rather to remove it alltogether?
I don't mind a conf file... Could you propose format for it so others could weight in here? I just think command line flags would stay and have precedence anyway.
I think I like idea of config (2) where flags just listed with values... And IMO quotes should be optional here... as semi-interesting outcome we may do comments allowed in...
We will probably have `--config filename` to read that config values as "defaults" for flags. Any flag given would override the config (as it now overrides defaults)
Yes, as you said pipelines are something that's already possible with current websocketd, something like ```websocketd bash -c './script | ./script'``` Similarly you can create bunch of scripts that implement...
We need to form middleware API here.... What actual things websocket knows that it can share with middleware about webclient to script link that's worth sharing.... What actions we want...