I assume you mean modules that rely on the same set of data, right? I do not talk explicitly about data transfer. But in several of the examples, you'll see how state is passed from one module to another. One way to do this is through configuration (external configuration
pattern). The extensibility patterns also talk about ways to make a module's behavior extensible. And state could easily be part of that behavior.
But this is a wonderful question because I simply present 18 modularity patterns. There are certainly other patterns out there. As I point out in the very first section of the book, I hope we see idioms emerge that show how to apply these patterns in different languages and using different module frameworks. I hope that we'll see tool support emerge that encourages modular design. And I hope that as others discover patterns that encourage modularity, they'll share them with us.
Visit the book's website at
modularity.kirkk.com where you can review all 18 patterns and download an excerpt of the book. There is also a
mobile web application available that you can take with you wherever you go.
--kirk
