Lines Matching refs:and
10 interprocess communication and network programming. This section
25 protocol: one using real DDE running on Windows only, and another
27 and virtually all of the behaviour is the same apart from the
34 DDE-based or socket-based implementation is used and the same
35 thing for {\tt wxClient} and {\tt wxConnection}.
44 equivalent wxTCP... and wxDDE... classes can be used in much the
50 \item wxClient. This represents the client application, and is used
52 \item wxServer. This represents the server application, and is used
55 client to the server - both the client and the server use an
61 variables: connection object, topic name and item name. A data
66 and a topic name to identify the topic for the duration of the
70 exist and will be deleted afterwards) in which case a Unix domain
77 The server then responds and either vetoes the connection or
78 allows it. If allowed, both the server and client objects create
80 closed. The connection object is then used for sending and
81 receiving subsequent messages between client and server -
94 argument. This member must create and return an instance of the
96 \item Create an instance of your server object and call Create to
108 create and return an instance of the derived connection class.
113 for local computer), service name, and topic name for this
141 send an OnAdvise message to the client along with the item and data.
144 The default data type is wxCF\_TEXT (ASCII text), and the default data
150 See the sample programs {\it server}\/ and {\it client}\/ in the IPC
152 using the Execute, Request, and Poke commands from the client, together
160 Windows and Unix).
163 you need to derive a class from wxConnection and another from
165 communications in a `conversation' with a server. and the custom
197 server is running on) and the server name (identifying the server
201 request for a connection is accepted, and the client then