3 ms·
Most of the problems in creating services by wrapping libraries in RPCs, in my experience, come from most libraries not supporting asynchrony, timeouts etc. Th
by nly 5y ago
Most of the problems in creating services by wrapping libraries in RPCs, in my experience, come from most libraries not supporting asynchrony, timeouts etc.
The zlib example is a bit baffling to be honest. If zlib goes in to an infinite 100% CPU loop, perhaps due to a zip bomb, you're still screwed as far as I can tell
A full RPC abstraction also gives you the opportunity to change out the backend implementation that this doesn't.
- AdmVonSchneider 5y ago> If zlib goes in to an infinite 100% CPU loop, perhaps due to a zip bomb, you're still screwed as far as I can tell You can set CPU and wall time limits and the sandbox will be killed if it runs for longer. > A full RPC abstraction also gives you the opportunity to change out the backend implementation that this doesn't. Absolutely, but the RPC mechanism in SAPI is an implementation detail and ideally not something you should have to care about. You can of course just use the Sandbox2 part of Sandboxed API and implement an RPC layer yourself.