| Proposal of a Standard to Solid OO Solution to Server-Side Architectures | ||
|---|---|---|
| Prev | Chapter 1. Introduction | Next |
XMLarizing objects: is the most original concept in my work. It is the concept of converting any object (XML or non-XML oriented) into XML input document, efficiently with small memory print, simply and fast. Since XML is today's language of information exchange, I believe that adaptation of this idea greatly improve both design of the applications and the actual execution performance as well.
DataInstance: provides complex solution to data entity representation. It unifies access to all data manipulation, which enables the possibility of easy component-ation of common functionality. The class diagram in figure 2.22 is a show case of such a intuitive functional component-ation. Remaining features of DataInstance completing the complexity of this solution are: object/data storage abstraction and DataInstance's metadata model.
Services: The notion of a service helps to separate the business logic functionality from the other implementation. What is new and benefit-able on this approach is the abstraction from the actual service implementation . When "ServiceMgr" is used, then all the components using the service are not impacted if the service implementation gets changed. One can use local implementation with direct service calls (within the same process) or remote method invocation and seamlessly swap all possible techniques without any impact on the rest of the application. It does not require any code changes nor restart of the server.
Complex design (becomingly identified components): when doing a design, there is always a reason (requirement), which initiates the project. It is natural, that the design is somehow specific to such requirement. When new requirement arises in the future, then new design is done. The requirement for my research project is to design generic architecture, which makes the future projects easier to build. When complete, building a project will consist of putting components together in very intuitive fashion.
Standard in server-side architectures: is my ultimate goal. My believes are, that if the ideas presented in this work would get accepted and become a standard, it would save a lot of work, a lot of lines of code and much headache with design development. I already have many positive feedbacks from the people using my proposed architecture.
XMLarized object: [eksmelera:jzd]: since the idea of "converting any object into XML input document" is a new technique, I encountered the absence of appropriate terminology. That is why I came up with the term "XMLarized object" pronounced [eksmelera:jzd].