I went to a technical salon on my weekend, the main content is about open source software framework applications and software architectures. That is very interesting to listen later. At present, my country's software has many platforms and programming languages, such as .NET J2EE, etc., there are corresponding frames in each language, such as Struts, AOP. . . Our programming generally does not need to start from scratch, but use a platform, give a framework, develop, now there are many frameworks, and it is not possible to apply. The problem should be paid attention to in the application. It is best to directly inherit it. Pojo object, we use it directly to use it without having to achieve a particular interface.
On the O / R mapping level, there are several better open source tools, such as JDO, Caster, Hibernate, which compare the Entity Bean compare Light-Weight, relatively simple. We have a lot of choices on this level, many middleware and platforms have this product. For example, our BV platform, he uses contentManager, ContentList, Content, BVI_GenericDbManager to perform our best database operation. In fact, it is said that these things are interoperability between abstract Object and Relationship Database in the language. The most commonly used is to use the SQL language directly. On this, we have graded the system, which is naturally this level. When we are settled, such as a Person class, we also define her PersonManager and PersonContainer class, we can abstract Person's incoming and deletion modification, such as adding a person to the database, we directly Call P.Save (); it is ok, even we can perform more abstraction to it. This time we need to give up the concept of the database, this time the database is transparent, the program is only It is good to use the corresponding function. At this time, the database is a larger Container, Container.Add (Person); In fact, we can have a lot of other container, which are loaded in memory, which can form their respective collections, which are not related to each other, these are just preliminary. We can inherit the Person class, and even define an IPerson interface, which is more beneficial for us to achieve their polymorphism. On this basis, we can achieve more object-oriented, more abstract environments.
A classmate tells me that in a relatively simple application of .NET, there is no Data Representation Layer, and the stored procedure is called directly with ASPX. . . Village has a trick in villages.
