The Trend Micro Management Communication Protocol (MCP) supports one-way and two-way communication.
NAT traversal has become an increasingly more significant issue in the current real-world network environment. To address this issue, MCP uses one-way communication. One-way communication has the MCP agent initiating the connection to, and polling of commands from, the server. Each request is a CGI-like command query or log transmission. To reduce the network impact, the MCP agent keeps connection alive and open as much as possible. A subsequent request uses an existing open connection. If the connection breaks, all SSL connections to the same host benefit from session ID cache that drastically reduces re-connection time.
Two-way communication is an alternative to one-way communication. Based on one-way communication but with an extra HTTP-based channel that receives server notifications, two-way communication can improve real time dispatching and processing of commands from the server by the MCP agent.