You might want to study design pattern in MVC :) It decoupling objects so that changes to one(model) can affect any number of others(views) without requiring the changed object to know details of the others ... To make it more reliability and scalablity you need read more info such as JMS(publish/subscribe messaging), j2ee(connector) and so on.Good luck!
JavaTM Message Service Tutorial 1.3 Beta Releasej2sdkee1.3 的文档--足够了！ ----这方面我了解也不多--只是皮毛大家一起学！
Messaging 是组件和应用程序之间互相通讯的一种方法！messaging 系统是一个对等的系统 ：每个客户端都连接到一个代理上，它提供了创建消息，发消息，收消息的功能，使任一个messaging 的客户端可以与其他客户端交换消息。 Messaging 以松耦合的方式实现分布式的通讯。一个组件发一个消息到一个已知的位置，需要接受消息的一端也从那里得到消息，也就是说，发送方和接受方不用同时在线，实施上，发方和收方彼此可以互不相知他们只需要知道消息的格式和那个已知的位置，在这种关系下，Messaging 区别于相对紧耦合的rmi! What Is Messaging? Messaging is a method of communication between software components or applications. A messaging system is a peer-to-peer facility: a messaging client can send messages to, and receive messages from, any other client. Each client connects to a messaging agent that provides facilities for creating, sending, and receiving messages. Messaging enables distributed communication that is loosely coupled. A component sends a message to a destination, and the recipient can retrieve it from the destination. However, the sender and receiver do not have to be available at the same time in order to communicate. In fact, the sender does not need to know anything about the receiver, nor does the receiver need to know anything about the sender; they only need to know what message format and what destination to use. In this respect, messaging differs from tightly coupled technologies such as Remote Method Invocation (RMI), which require an application to know a remote application's methods. Messaging also differs from electronic mail (e-mail), which is a method of communication between people, or between software applications and people. Messaging is used for communication between software applications or software components.
It decoupling objects so that changes to one(model) can affect any number of others(views) without requiring the changed object to know details of the others ... To make it more reliability and scalablity you need read more info such as JMS(publish/subscribe messaging), j2ee(connector) and so on.Good luck!
-----------------jms真有用呀！---还是jms好！
顺便问一句，如果用jms的话，我该看看哪些方面的资料？指点指点哦。
：每个客户端都连接到一个代理上，它提供了创建消息，发消息，收消息的功能，使任一个messaging 的客户端可以与其他客户端交换消息。
Messaging 以松耦合的方式实现分布式的通讯。一个组件发一个消息到一个已知的位置，需要接受消息的一端也从那里得到消息，也就是说，发送方和接受方不用同时在线，实施上，发方和收方彼此可以互不相知他们只需要知道消息的格式和那个已知的位置，在这种关系下，Messaging 区别于相对紧耦合的rmi!
What Is Messaging?
Messaging is a method of communication between software components or applications. A messaging system is a peer-to-peer facility: a messaging client can send messages to, and receive messages from, any other client. Each client connects to a messaging agent that provides facilities for creating, sending, and receiving messages.
Messaging enables distributed communication that is loosely coupled. A component sends a message to a destination, and the recipient can retrieve it from the destination. However, the sender and receiver do not have to be available at the same time in order to communicate. In fact, the sender does not need to know anything about the receiver, nor does the receiver need to know anything about the sender; they only need to know what message format and what destination to use. In this respect, messaging differs from tightly coupled technologies such as Remote Method Invocation (RMI), which require an application to know a remote application's methods. Messaging also differs from electronic mail (e-mail), which is a method of communication between people, or between software applications and people. Messaging is used for communication between software applications or software components.
谢谢大虾！！