- A wxServer object represents the server part of a client-server
- DDE-like (Dynamic Data Exchange) conversation. The actual
- DDE-based implementation using wxDDEServer is available on Windows
- only, but a platform-independent, socket-based version of this
- API is available using wxTCPServer, which has the same API.
-
- To create a server which can communicate with a suitable client,
- you need to derive a class from wxConnection and another from
- wxServer. The custom wxConnection class will intercept
- communications in a 'conversation' with a client, and the custom
- wxServer is required so that a user-overridden wxServer::OnAcceptConnection
- member can return a wxConnection of the required class, when a
- connection is made. Look at the IPC sample and the @ref overview_ipcoverview
- "Interprocess communications overview" for
- an example of how to do this.
+ A wxServer object represents the server part of a client-server DDE-like
+ (Dynamic Data Exchange) conversation. The actual DDE-based implementation
+ using wxDDEServer is available on Windows only, but a platform-independent,
+ socket-based version of this API is available using wxTCPServer, which has
+ the same API.
+
+ To create a server which can communicate with a suitable client, you need to
+ derive a class from wxConnection and another from wxServer.
+ The custom wxConnection class will intercept communications in a 'conversation'
+ with a client, and the custom wxServer is required so that a user-overridden
+ wxServer::OnAcceptConnection member can return a wxConnection of the required
+ class, when a connection is made.
+ Look at the IPC sample and the @ref overview_ipc for an example of how to do this.