isesoft1,
Thank you. We try to do our best. Here are comments:
- BMP: module as actually some kind of platform for BMP but it has to be build manually.
- AOP: I'm not sure which AOP you think, if this is Aspect-oriented programming then this technique is used internally when needed. All functionalities related to dnn framework (without interfaces) are implemented using this approach (it is only possible solution). Internally we used mixed approach but mostly not AOP.
- business programmable: I'm not sure about this. This module is actually GUI that relies on independent component. You can access component programmatically for server-side programming. Anyway, it is not possible to use full "business tier" logic there because of philosophy we use for component/module. Classic business logic require data within business layer for treatment - most of other modules uses same approach, but this is not the case for this module because this require couple of millions record for larger database transfered from db server. Module actually tries to convert business logic to appropriate sql statements - with this eliminates unwanted data transfer and speed-up process because databases are actually much more optimized for working with larger datasets than .net framework (which can be used within business tier in this environment).
N-Tier: Internally there is already n-tier philosophy implemented (according to limitations from previous line). This is reason why you can change underlying database (ms-sql, access, mysql, etc). If you use objects programmatically then you can use object for business tier that is called "data" (and dependent objects). You can also use these object on remote machine where db is(all should be serializable) for avoiding large data transfer.
Kind regards,
Primoz