Talk:Module (TinyMUX)

Since this has few to no dependencies on TinyMUX itself and could be used elsewhere, should we change libmux, mux_*, and MUX_* names to something else?

The consensus is that mux_ModuleTick() should be named for what it does instead of its calling pattern, so mux_ModuleTick() has been renamed mux_ModuleMaintenance().

The out-of-proc details and diagrams need to be added.

If a module has active component instances, the interfaces are revoked, but the module cannot be completely unloaded. Is there a mechanism for accomplishing this after the last instance is finally released? Oh! I think that occurs by virtue of mux_ModuleTick() being called periodically.