Now, the open-source xeim case project "LAN chat" has adopted the alpha version of apworks, and has made some implementations in commandhandler and eventhandler. Before downloading and compiling "LAN chat", download and install apworks Alpha. If your apworks is not installed in the C:/Program Files directory, you need to re-add references to apworks in the "LAN chat" project.
The framework needs to be followed so that the convenience brought by the framework can be used to solve practical problems. However, software is not as simple as you think. The business varies widely, and the demand for specific services is ever-changing. How can we use a framework to limit the development of application systems? Indeed. Although apworks is a framework, it can implement applications based on the xeim architecture.ProgramBut not most (or even all) application system development needs to use the apworks framework, and must be applied to the xeim architecture. The classic application system architecture model is still very popular, and many successful cases still use the classic system architecture model. This architecture mode can be roughly described using the following view (this figure is taken from Greg Young's xeim documents ):
This architecture is simple first: It is quite common, and nearly 80% of "LAN chat" projects can be designed using this structure, which is very easy for developers to understand, therefore, the threshold is relatively low. Because it is simple and common, there will be a series of tools to support the development of applications based on this structure (such as ORM ), greatly increased productivity (from Greg Young's xeim documents ). Therefore, I would like to make a decision on your application system architecture based on your needs, and then select the technology. Last week, I had a chat with my friends about the xeim mode. They were all surprised that the relational database would actually be "dispensable. A friend asked me: What should I do if I find my system is not suitable for xeim style? I said: Do not use xeim, because it is not suitable for you! Therefore, I think the deeper meaning of the no framework lies in this: do not influence your judgment on the system requirements and architecture style because of the Framework. Do not use the framework alone.