It's really miserable, so long to log in for the second time!
These days have been learned PB, just learned Easerver, trying multi-storey development. It is only a general understanding, there are still many problems in specific implementation.
EA Server is used as an application intermediate layer that allows client connections to a variety of ways. For example, PB, JSP (ASP). Method to realize:
1. First establish an application component (the main implementation of the Component application, implement the connection, data processing of the database, etc.), and create a corresponding method, then release
2. Then establish an application agent (Proxy)
This agent contains the interface part of the server component method, mainly for client development, implementation of the method of server components.
3. Client
Depending on the description of Proxy, the method of the server component can be called directly in the application to implement business logic (?).
Since Proxy is a static, if the server component has a big change, you must regenerate Proxy.
At present, I have encountered some problems, for example, using the PB program as the client, implementing the data retrieval, but I don't know how to implement data updates. When retrieving, the client does not need to specify DataObject, but it is not known to be set when it is updated to implement data entry (data update actually knows how to implement).
According to your current understanding, everyone is more keen to make the server components into WebServices, the client adopts JSP, ASP implementation B / S architecture
. So I will learn how JSP, how the ASP implements communication with Easerver.
Hey, there is too much to learn, come slowly, strive to make progress every day :)
