DDE-based or socket-based implementation is used and the same
thing for {\tt wxClient} and {\tt wxConnection}.
-By default, DDE implementation is used under Windows. DDE works
-only within one computer. If you want to use IPC between
+By default, the DDE implementation is used under Windows. DDE works
+within one computer only. If you want to use IPC between
different workstations you should define {\tt
wxUSE\_DDE\_FOR\_IPC} as $0$ before including this header -- this
will force using TCP/IP implementation even under Windows.
exist and will be deleted afterwards) in which case a Unix domain
socket is created.
-{\bf SECURITY NOTE:} Using Internet domain sockets if extremely insecure for
+{\bf SECURITY NOTE:} Using Internet domain sockets is extremely insecure for
IPC as there is absolutely no access control for them, use Unix domain sockets
whenever possible!
\item Use the wxConnection member functions to send messages to the server.
\end{enumerate}
-\subsection{Data transfer}
+\subsection{Data transfer}\label{datatransfer}
These are the ways that data can be transferred from one
application to another. These are methods of wxConnection.
size is the length of the null-terminated string. Windows-specific data
types could also be used on the PC.
-\subsection{Examples}
+\subsection{Examples}\label{ipcexamples}
See the sample programs {\it server}\/ and {\it client}\/ in the IPC
samples directory. Run the server, then the client. This demonstrates
with an Advise loop: selecting an item in the server list box causes
that item to be highlighted in the client list box.
-\subsection{More DDE details}
+\subsection{More DDE details}\label{ddedetails}
A wxClient object initiates the client part of a client-server
DDE-like (Dynamic Data Exchange) conversation (available in both
\end{verbatim}
Note that it is no longer necessary to call wxDDEInitialize or wxDDECleanUp, since
-wxWidgets will do this itself if necessary.
+wxWidgets will do this by itself if necessary.