On Fri, 19 Jul 2002 13:57:22 EDT, David Wheeler <dwheelerat_private> said: > Chris rightly stated that someone should create a > "stacking" module. So, I've started to do just that. > I'll post my first draft soon. Now, I understand how (at least conceptually) you could stack modules that are addressing different areas - for instance, a module for *just* the network hooks and a module for resource limits could co-exist easily enough. But how do you intend to handle composition of functions if they're in the *same* area? I thought for a moment that a rule like "a module can't grab a hook that's already in use by a previously stacked module", but that's a non-starter (for instance, if the first module only cares about open() and the second wants open() and mmap(), you're stuck). I think this was the issue that made any sort of generalized stacking impractical? On the other hand, it might be useful to have a framework to support "chinese menu" modules - pick one from column A, 2 from B, and 1 from C *IF* it was an entire system with components designed to work that way. Is that what you're looking at? -- Valdis Kletnieks Computer Systems Senior Engineer Virginia Tech
This archive was generated by hypermail 2b30 : Fri Jul 19 2002 - 11:37:34 PDT