QuoteOriginally posted by: CuchulainnQuoteOriginally posted by: CuchulainnQuoteOriginally posted by: outrunQuoteOriginally posted by: CuchulainnQuoteOriginally posted by: outrunI'm saying that signals is *library*, the design can also e.g. be done compile-time without using signals at all.First, we can design (on paper) to find the modules and interfaces, the use Boost to implement my design.yes! But that's what you are doing already, right?I think the role of "signals" in your design was/is not clear to everyone and this single sentence already helps a lot: it's show that the two are not the same (design, and using signals) which wasn't always clear.Maybe you also use signals as a design concept (abstract of implementation) instead of a signals as a library choice (with its specific interfaces that you can look up in the code ref manual)? You mentioned software as hardware or something, that I liked a lot. In our algo-engine design we talked about publishers and subscribers (like newspapers) to keep the design talk free of specific implementation library choices. A publisher could have multiple subscribers etc. We tried many terminologies, but they kept causing confusion because we discussed the design on so many levels (including implementation possibilities) edit:E.g. can you define the design? You compare it in the context of GOF with the list of features that relate a lot to OO design element (like inheritance), but that's mainly because you compare it against OO. Can you also define it in itself? Can the design also be used in non-OO languages, -I'm saying yes- e.g. I can build an Excel worksheet and mark cell ranges as modules or variables, and link things up with cell references.Edit2:The hardware as software concept shows that it's about wel defined interfaces and communicating on those via a glue mechanism. It very suitable for various layers, also linking up modules running on different machines, and an alternative implementation of the same design could be done on top of asio, right?Here is a very good review of 3 different kinds of architectures. This is front-end to C++/C#ftp://db.stanford.edu/pub/cstr/reports/ ... 95-674.pdf
QuoteThree Concepts of System Architecture 1 Introductionftp://db.stanford.edu/pub/.../CSL-TR-95-674.pdf - Vertaal deze paginaBestandsformaat: PDF/Adobe Acrobat - Snelle weergavedoor DC Luckham - 1995 - Geciteerd door 82 - Verwante artikelenDavid C. Luckham ... face connection architecture, and plug and socket architecture. ... services service connection , are introduced to de ne plug and socket ... See my article on mapping this arch to OO language.