3 ms·
The executable has really simple output--it either works and outputs json, or doesn't and outputs nothing--so there's no difficulty with error handling. I guess
by danenania 9y ago
The executable has really simple output--it either works and outputs json, or doesn't and outputs nothing--so there's no difficulty with error handling. I guess I can understand wanting tighter integration for more complex scenarios though... an http server is an interesting idea, but could you run into issues with ports being restricted on production servers?
I'm not seeing any performance issues with stdout, but I'm also not writing much data.
- tokenizerrr 9y ago> but could you run into issues with ports being restricted on production servers Sorry, what? Just make the port configurable?
- danenania 9y agoIt was a question (note the question mark)... I don't see the need for snark. Anyway, for my purposes, this wouldn't work, since the executable is embedded in libraries that are meant to run anywhere without any configuration. But yeah I could see that being fine under other circumstances I guess.
- tokenizerrr 9y agoNo snark. Just puzzled. You can still just make it configurable. Or just pick a random port and communicate it with your child process.