3 ms·
I built this library to deal with OpenOffice's PyUNO service hanging, leaking memory, and not being thread-safe. I think it could be quite useful for people run
by BenjaminCoe 15y ago
I built this library to deal with OpenOffice's PyUNO service hanging, leaking memory, and not being thread-safe. I think it could be quite useful for people running into similar problems.
- ComputerGuru 15y agoI'm not familiar with PyUNO so forgive me if this is way out there, but would placing PyUNO behind a ZMQ gateway then using ZMQ for communication with your frontend work?
- BenjaminCoe 15y agoThe somewhat weird use-case that I'm solving for PyUno is that the OpenOffice service leaks memory like a sieve. With the hooks built into TCPLock, I can periodically kill OpenOffice and hold off an accepting more connections until the service is available on port 8100 again. I don't know enough about ZMQ to speak to it, but I'm sure I could wire something together to solve this problem using any number of approaches. A proxy in Node.js was tempting because it's simple, lightweight, and does the trick quite nicely :)
- ComputerGuru 15y agoI had misunderstood. I thought you were using the semaphore to allow only one request at a time so as to avoid/mitigate the memory leak, not pend all requests during a restart of OO.
- diego 15y agoThat case it's not weird, in fact it's a relatively common pattern. See: http://zguide.zeromq.org/page:all#header-15 http://zguide.zeromq.org/page:all#header-15
- tudd 15y agoThis is why I love you guys. Instead of solving the problem, you trade it for a new problem.