Confirm
699
edits
Changes
→Implementation
'''NOTE''': I think it's worthwhile leaving error detection on even in optimized builds. It should be quite cheap compared to IPC overhead and will likely allow us to avoid security-related bugs.
An ''actor'' will just be an instance of a protocol server or client class. We need some way of addressing particular actors across threads and processes. Hopefully the chromium IPC code already supports this. Also, we can easily support process-to-process and thread-to-thread communication over these protocols. The latter would be very useful for debugging, and also useful for writing threaded code that avoids shared memory as much as possible (even when we have multiple processes we will still have multiple threads).
I '''do not''' think that protocol instances should be thread safe (in the usual shared-memory sense). We should use these protocols to avoid this kind of threaded code, whether in-process or out-of-process.
