fixed broken link

[wxWidgets.git] / docs / latex / wx / socket.tex

diff --git a/docs/latex/wx/socket.tex b/docs/latex/wx/socket.tex
index f4e8f7df05654cf92a9e0cc358bfc5570cdb5c6d..9bede77f47e97d44f125724e6ed436d185b671f9 100644 (file)
--- a/docs/latex/wx/socket.tex
+++ b/docs/latex/wx/socket.tex
@@ -1,415 +1,500 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%% Name:        socket.tex
+%% Purpose:     wxSocket docs
+%% Author:      Guillermo Rodriguez Garcia <guille@iies.es>
+%% Modified by:
+%% Created:     1999
+%% RCS-ID:      $Id$
+%% Copyright:   (c) wxWindows team
+%% License:     wxWindows license
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+

 \section{\class{wxSocketBase}}\label{wxsocketbase}
 
 \section{\class{wxSocketBase}}\label{wxsocketbase}
 

+wxSocketBase is the base class for all socket-related objects, and it
+defines all basic IO functionality.
+

 \wxheading{Derived from}
 
 \wxheading{Derived from}
 

-\helpref{wxEvtHandler}{wxevthandler}
+\helpref{wxObject}{wxobject}

 
 

-% ---------------------------------------------------------------------------
-% Event handling
-% ---------------------------------------------------------------------------
-\wxheading{Event handling}
+\wxheading{Include files}

 
 

-To process events from a socket, use the following event handler macro to direct
- input to member
-functions that take a \helpref{wxSocketEvent}{wxsocketevent} argument.
+<wx/socket.h>

 
 

-\twocolwidtha{7cm}%
+\wxheading{wxSocket errors}
+
+\twocolwidtha{7cm}

 \begin{twocollist}\itemsep=0pt
 \begin{twocollist}\itemsep=0pt

-\twocolitem{{\bf EVT\_SOCKET(id, func)}}{A socket event occured.}
-\end{twocollist}%
+\twocolitem{{\bf wxSOCKET\_NOERROR}}{No error happened.}
+\twocolitem{{\bf wxSOCKET\_INVOP}}{Invalid operation.}
+\twocolitem{{\bf wxSOCKET\_IOERR}}{Input/Output error.}
+\twocolitem{{\bf wxSOCKET\_INVADDR}}{Invalid address passed to wxSocket.}
+\twocolitem{{\bf wxSOCKET\_INVSOCK}}{Invalid socket (uninitialized).}
+\twocolitem{{\bf wxSOCKET\_NOHOST}}{No corresponding host.}
+\twocolitem{{\bf wxSOCKET\_INVPORT}}{Invalid port.}
+\twocolitem{{\bf wxSOCKET\_WOULDBLOCK}}{The socket is non-blocking and the operation would block.}
+\twocolitem{{\bf wxSOCKET\_TIMEDOUT}}{The timeout for this operation expired.}
+\twocolitem{{\bf wxSOCKET\_MEMERR}}{Memory exhausted.}
+\end{twocollist}

 
 

-% ---------------------------------------------------------------------------
-% See also ...
-% ---------------------------------------------------------------------------
-\wxheading{See also}
+\wxheading{wxSocket events}

 
 

-\helpref{wxSocketEvent}{wxsocketevent}\\
-\helpref{wxSocketClient}{wxsocketclient}\\
-\helpref{wxSocketServer}{wxsocketserver}
-
-% ---------------------------------------------------------------------------
-% Members
-% ---------------------------------------------------------------------------
-\latexignore{\rtfignore{\wxheading{Members}}}
+\twocolwidtha{7cm}
+\begin{twocollist}\itemsep=0pt
+\twocolitem{{\bf wxSOCKET\_INPUT}}{There is data available for reading.}
+\twocolitem{{\bf wxSOCKET\_OUTPUT}}{The socket is ready to be written to.}
+\twocolitem{{\bf wxSOCKET\_CONNECTION}}{Incoming connection request (server), or successful connection establishment (client).}
+\twocolitem{{\bf wxSOCKET\_LOST}}{The connection has been closed.}
+\end{twocollist}

 
 

-\membersection{wxSocketBase::wxSocketBase}
+A brief note on how to use these events:
+
+The {\bf wxSOCKET\_INPUT} event will be issued whenever there is data
+available for reading. This will be the case if the input queue was
+empty and new data arrives, or if the application has read some data
+yet there is still more data available. This means that the application
+does not need to read all available data in response to a 
+{\bf wxSOCKET\_INPUT} event, as more events will be produced as
+necessary.
+
+The {\bf wxSOCKET\_OUTPUT} event is issued when a socket is first
+connected with \helpref{Connect}{wxsocketclientconnect} or accepted
+with \helpref{Accept}{wxsocketserveraccept}. After that, new
+events will be generated only after an output operation fails
+with {\bf wxSOCKET\_WOULDBLOCK} and buffer space becomes available
+again. This means that the application should assume that it
+can write data to the socket until an {\bf wxSOCKET\_WOULDBLOCK} 
+error occurs; after this, whenever the socket becomes writable
+again the application will be notified with another 
+{\bf wxSOCKET\_OUTPUT} event.
+
+The {\bf wxSOCKET\_CONNECTION} event is issued when a delayed connection
+request completes successfully (client) or when a new connection arrives
+at the incoming queue (server).
+
+The {\bf wxSOCKET\_LOST} event is issued when a close indication is
+received for the socket. This means that the connection broke down or
+that it was closed by the peer. Also, this event will be issued if
+a connection request fails.

 
 

-\func{}{wxSocketBase}{\void}
+\wxheading{Event handling}

 
 

-Default constructor but don't use it, you must use \helpref{wxSocketClient}{wxsocketclient}
-or \helpref{wxSocketServer}{wxsocketserver}.
+To process events coming from a socket object, use the following event
+handler macro to direct events to member functions that take
+a \helpref{wxSocketEvent}{wxsocketevent} argument.

 
 

-\membersection{wxSocketBase::\destruct{wxSocketBase}}
+\twocolwidtha{7cm}%
+\begin{twocollist}\itemsep=0pt
+\twocolitem{{\bf EVT\_SOCKET(id, func)}}{Process a wxEVT\_SOCKET event.}
+\end{twocollist}

 
 

-\func{}{\destruct{wxSocketBase}}{\void}
+\wxheading{See also}

 
 

-Destroys the wxSocketBase object.
+\helpref{wxSocketEvent}{wxsocketevent}, 
+\helpref{wxSocketClient}{wxsocketclient}, 
+\helpref{wxSocketServer}{wxsocketserver}, 
+\helpref{Sockets sample}{samplesockets}

 
 % ---------------------------------------------------------------------------
 
 % ---------------------------------------------------------------------------

-% State functions
+% Function groups

 % ---------------------------------------------------------------------------
 
 % ---------------------------------------------------------------------------
 

-\membersection{wxSocketBase::Ok}\label{wxsocketbaseok}
+\latexignore{\rtfignore{\wxheading{Function groups}}}

 
 

-\constfunc{bool}{Ok}{\void}
+\membersection{Construction and destruction}

 
 

-Returns TRUE if the socket is initialized and ready and FALSE in other
-cases.
+\helpref{wxSocketBase}{wxsocketbaseconstruct}\\
+\helpref{\destruct{wxSocketBase}}{wxsocketbasedestruct}\\
+\helpref{Destroy}{wxsocketbasedestroy}

 
 

-\membersection{wxSocketBase::Error}\label{wxsocketbaseerror}
+\membersection{Socket state}

 
 

-\constfunc{bool}{Error}{\void}
+Functions to retrieve current state and miscellaneous info.

 
 

-Returns TRUE if an error occured.
+\helpref{Error}{wxsocketbaseerror}\\
+\helpref{GetLocal}{wxsocketbasegetlocal}\\
+\helpref{GetPeer}{wxsocketbasegetpeer}
+\helpref{IsConnected}{wxsocketbaseisconnected}\\
+\helpref{IsData}{wxsocketbaseisdata}\\
+\helpref{IsDisconnected}{wxsocketbaseisdisconnected}\\
+\helpref{LastCount}{wxsocketbaselastcount}\\
+\helpref{LastError}{wxsocketbaselasterror}\\
+\helpref{Ok}{wxsocketbaseok}\\
+\helpref{SaveState}{wxsocketbasesavestate}\\
+\helpref{RestoreState}{wxsocketbaserestorestate}

 
 

-\membersection{wxSocketBase::IsConnected}\label{wxsocketbaseconnected}
+\membersection{Basic IO}

 
 

-\constfunc{bool}{IsConnected}{\void}
+Functions that perform basic IO functionality.

 
 

-Returns TRUE if the socket is connected.
+\helpref{Close}{wxsocketbaseclose}\\
+\helpref{Discard}{wxsocketbasediscard}\\
+\helpref{Peek}{wxsocketbasepeek}\\
+\helpref{Read}{wxsocketbaseread}\\
+\helpref{ReadMsg}{wxsocketbasereadmsg}\\
+\helpref{Unread}{wxsocketbaseunread}\\
+\helpref{Write}{wxsocketbasewrite}\\
+\helpref{WriteMsg}{wxsocketbasewritemsg}

 
 

-\membersection{wxSocketBase::IsData}\label{wxsocketbaseisdata}
+Functions that perform a timed wait on a certain IO condition.

 
 

-\constfunc{bool}{IsData}{\void}
+\helpref{InterruptWait}{wxsocketbaseinterruptwait}\\
+\helpref{Wait}{wxsocketbasewait}\\
+\helpref{WaitForLost}{wxsocketbasewaitforlost}\\
+\helpref{WaitForRead}{wxsocketbasewaitforread}\\
+\helpref{WaitForWrite}{wxsocketbasewaitforwrite}\\

 
 

-Returns TRUE if some data is arrived on the socket. 
+and also:

 
 

-\membersection{wxSocketBase::IsDisconnected}\label{wxsocketbasedisconnected}
+\helpref{wxSocketServer::WaitForAccept}{wxsocketserverwaitforaccept}\\
+\helpref{wxSocketClient::WaitOnConnect}{wxsocketclientwaitonconnect}

 
 

-\constfunc{bool}{IsDisconnected}{\void}
+Functions that allow applications to customize socket IO as needed.

 
 

-Returns TRUE if the socket is disconnected.
+\helpref{GetFlags}{wxsocketbasegetflags}\\
+\helpref{SetFlags}{wxsocketbasesetflags}\\
+\helpref{SetTimeout}{wxsocketbasesettimeout}

 
 

-\membersection{wxSocketBase::IsNoWait}\label{wxsocketbasenowait}
+\membersection{Handling socket events}

 
 

-\constfunc{bool}{IsNoWait}{\void}
+Functions that allow applications to receive socket events.

 
 

-Returns TRUE if the socket mustn't wait.
+\helpref{Notify}{wxsocketbasenotify}\\
+\helpref{SetNotify}{wxsocketbasesetnotify}\\
+\helpref{GetClientData}{wxsocketbasegetclientdata}\\
+\helpref{SetClientData}{wxsocketbasesetclientdata}\\
+\helpref{SetEventHandler}{wxsocketbaseseteventhandler}

 
 

-\membersection{wxSocketBase::LastCount}\label{wxsocketbaselastcount}
+Callback functions are also available, but they are provided for backwards
+compatibility only. Their use is strongly discouraged in favour of events,
+and should be considered deprecated. Callbacks may be unsupported in future
+releases of wxWindows.

 
 

-\constfunc{size\_t}{LastCount}{\void}
+\helpref{Callback}{wxsocketbasecallback}\\
+\helpref{CallbackData}{wxsocketbasecallbackdata}

 
 

-Returns the number of bytes read or written by the last IO call.
-
-\membersection{wxSocketBase::LastError}\label{wxsocketbaselasterror}
-
-\constfunc{int}{LastError}{\void}
-
-Returns an error in the errno format (see your C programmer's guide).

 
 % ---------------------------------------------------------------------------
 
 % ---------------------------------------------------------------------------

-% IO calls
+% Members here

 % ---------------------------------------------------------------------------
 % ---------------------------------------------------------------------------

-%
-% Peek
-%
-\membersection{wxSocketBase::Peek}\label{wxsocketbasepeek}

 
 

-\func{wxSocketBase\&}{Peek}{\param{char *}{ buffer}, \param{size\_t}{ nbytes}}
+\helponly{\insertatlevel{2}{

 
 

-This function peeks a buffer of {\it nbytes} bytes from the socket. Peeking a buffer
-doesn't delete it from the system socket in-queue.
+\wxheading{Members}

 
 

-\wxheading{Parameters}
+}}

 
 

-\docparam{buffer}{Buffer where to put peeked data.}
+\membersection{wxSocketBase::wxSocketBase}\label{wxsocketbaseconstruct}

 
 

-\docparam{nbytes}{Number of bytes.}
+\func{}{wxSocketBase}{\void}

 
 

-\wxheading{Return value}
+Default constructor. Don't use it directly; instead, use 
+\helpref{wxSocketClient}{wxsocketclient} to construct a socket client, or 
+\helpref{wxSocketServer}{wxsocketserver} to construct a socket server.

 
 

-Returns a reference to the current object.
+\membersection{wxSocketBase::\destruct{wxSocketBase}}\label{wxsocketbasedestruct}

 
 

-\wxheading{See also}
+\func{}{\destruct{wxSocketBase}}{\void}

 
 

-\helpref{wxSocketBase::Error}{wxsocketbaseerror}\\
-\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}\\
-\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}
+Destructor. Do not destroy a socket using the delete operator directly;
+use \helpref{Destroy}{wxsocketbasedestroy} instead. Also, do not create
+socket objects in the stack.

 
 %
 
 %

-% Read
+% Callback

 %
 %

-\membersection{wxSocketBase::Read}\label{wxsocketbaseread}
-
-\func{wxSocketBase\&}{Read}{\param{char *}{ buffer}, \param{size\_t}{ nbytes}}
+\membersection{wxSocketBase::Callback}\label{wxsocketbasecallback}

 
 

-This function reads a buffer of {\it nbytes} bytes from the socket.
+\func{wxSocketBase::wxSockCbk}{Callback}{\param{wxSocketBase::wxSockCbk}{ callback}}

 
 

-\wxheading{Parameters}
+You can setup a callback function to be called when an event occurs.
+The function will be called only for those events for which notification
+has been enabled with \helpref{Notify}{wxsocketbasenotify} and 
+\helpref{SetNotify}{wxsocketbasesetnotify}. The prototype of the
+callback must be as follows:

 
 

-\docparam{buffer}{Buffer where to put read data.}
+\begin{verbatim}
+void SocketCallback(wxSocketBase& sock, wxSocketNotify evt, char *cdata);
+\end{verbatim}

 
 

-\docparam{nbytes}{Number of bytes.}
+The first parameter is a reference to the socket object in which the
+event occurred. The second parameter tells you which event occurred.
+(See \helpref{wxSocket events}{wxsocketbase}). The third parameter
+is the user data you specified using \helpref{CallbackData}{wxsocketbasecallbackdata}.

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns a reference to the current object.
+A pointer to the previous callback.

 
 \wxheading{Remark/Warning}
 
 
 \wxheading{Remark/Warning}
 

-By default, Read uses an internal asynchronous manager: it will send data when
-the socket requests them. It is particularly interesting when you enter a long
-data transfer (e.g. a big file, an image, ...). But it is also buggy when you
-simply discuss with the peer using user data. In this case, wxSocket prepares
-itself to send data (Write wait for them to be sent) and during a GUI refresh
-the user enters new data, which involves a new Read call though the previous
-isn't finished. Well, in most cases it can work but it might fail too.
-So I advise you to use the SPEED flag, which disables the asynchronous manager,
-when you just want to discuss with the peer.
-
-This remark is also valid for all IO call.
+Note that callbacks are now deprecated and unsupported, and they remain
+for backwards compatibility only. Use events instead.

 
 \wxheading{See also}
 
 
 \wxheading{See also}
 

-\helpref{wxSocketBase::Error}{wxsocketbaseerror},
- \helpref{wxSocketBase::LastCount}{wxsocketbaselastcount},
- \helpref{wxSocketBase::LastError}{wxsocketbaselasterror}
- 
-\membersection{wxSocketBase::SetFlags}\label{wxsocketbasesetflags}
-
-\func{void}{SetFlags}{\param{wxSockFlags}{ flags}}
-
-\twocolwidtha{7cm}
-\begin{twocollist}\itemsep=0pt
-\twocolitem{{\bf wxSocketBase::NONE}}{Normal functionnalities.}
-\twocolitem{{\bf wxSocketBase::NOWAIT}}{Get the available data in the input queue and exit immediately.}
-\twocolitem{{\bf wxSocketBase::WAITALL}}{Wait for all required data unless an error occured.}
-\twocolitem{{\bf wxSocketBase::SPEED}}{Disable the asynchronous IO functionnality.}
-\end{twocollist}
+\helpref{wxSocketBase::CallbackData}{wxsocketbasecallbackdata}, 
+\helpref{wxSocketBase::SetNotify}{wxsocketbasesetnotify}, 
+\helpref{wxSocketBase::Notify}{wxsocketbasenotify}

 
 %
 
 %

-% Read
+% CallbackData

 %
 %

-\membersection{wxSocketBase::Write}\label{wxsocketbasewrite}
-
-\func{wxSocketBase\&}{Write}{\param{const char *}{ buffer}, \param{size\_t}{ nbytes}}
-
-This function writes a buffer of {\it nbytes} bytes from the socket.
-
-\wxheading{Remark/Warning}
+\membersection{wxSocketBase::CallbackData}\label{wxsocketbasecallbackdata}

 
 

-By default, Write uses an internal asynchronous manager: it will send data when
-the socket requests them. It is particularly interesting when you enter a long
-data transfer (e.g. a big file, an image, ...). But it is also buggy when you
-simply discuss with the peer using user data. In this case, wxSocket prepares
-itself to send data (Write wait for them to be sent) and during a GUI refresh
-the user enters new data, which involves a new Write call though the previous
-isn't finished. Well, in most cases it can work but it might fail too.  
-So I advise you to use the SPEED flag, which disables the asynchronous manager,
-when you just want to discuss with the peer.
+\func{char *}{CallbackData}{\param{char *}{cdata}}

 
 

-\wxheading{Parameters}
+This function sets the the user data which will be passed to a
+callback function set via \helpref{Callback}{wxsocketbasecallback}.

 
 

-\docparam{buffer}{Buffer where to get the data to write.}
+\wxheading{Return value}

 
 

-\docparam{nbytes}{Number of bytes.}
+A pointer to the previous user data.

 
 

-\wxheading{Return value}
+\wxheading{Remark/Warning}

 
 

-Returns a reference to the current object.
+Note that callbacks are now deprecated and unsupported, and they remain
+for backwards compatibility only. Use events instead.

 
 \wxheading{See also}
 
 
 \wxheading{See also}
 

-\helpref{wxSocketBase::Error}{wxsocketbaseerror}\\
-\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}\\
-\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}
+\helpref{wxSocketBase::Callback}{wxsocketbasecallback}, 
+\helpref{wxSocketBase::SetNotify}{wxsocketbasesetnotify}, 
+\helpref{wxSocketBase::Notify}{wxsocketbasenotify}

 
 %
 
 %

-% WriteMsg
+% Close

 %
 %

-\membersection{wxSocketBase::WriteMsg}\label{wxsocketbasewritemsg}
+\membersection{wxSocketBase::Close}\label{wxsocketbaseclose}

 
 

-\func{wxSocketBase\&}{WriteMsg}{\param{const char *}{ buffer}, \param{size\_t}{ nbytes}}
+\func{void}{Close}{\void}

 
 

-This function writes a buffer of {\it nbytes} bytes from the socket. But it
-writes a short header before so that ReadMsg can alloc the right size for
-the buffer. So a buffer sent with WriteMsg {\bf must} be read with ReadMsg.
+This function shuts down the socket, disabling further transmission and
+reception of data; it also disables events for the socket and frees the
+associated system resources. Upon socket destruction, Close is automatically
+called, so in most cases you won't need to do it yourself, unless you
+explicitly want to shut down the socket, typically to notify the peer
+that you are closing the connection.

 
 

-\wxheading{Parameters}
+\wxheading{Remark/Warning}

 
 

-\docparam{buffer}{Buffer where to put data peeked.}
+Although Close immediately disables events for the socket, it is possible
+that event messages may be waiting in the application's event queue. The
+application must therefore be prepared to handle socket event messages
+even after calling Close.

 
 

-\docparam{nbytes}{Number of bytes.}
+%
+% Destroy
+%
+\membersection{wxSocketBase::Destroy}\label{wxsocketbasedestroy}

 
 

-\wxheading{Return value}
+\func{bool}{Destroy}{\void}

 
 

-Returns a reference to the current object.
+Destroys the socket safely. Use this function instead of the delete operator,
+since otherwise socket events could reach the application even after the
+socket has been destroyed. To prevent this problem, this function appends
+the wxSocket to a list of object to be deleted on idle time, after all
+events have been processed. For the same reason, you should avoid creating
+socket objects in the stack.

 
 

-\wxheading{See also}
+Destroy calls \helpref{Close}{wxsocketbaseclose} automatically.

 
 

-\helpref{wxSocketBase::Error}{wxsocketbaseerror}\\
-\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}\\
-\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}\\
-\helpref{wxSocketBase::ReadMsg}{wxsocketbasereadmsg}
+\wxheading{Return value}
+
+Always true.

 
 %
 
 %

-% ReadMsg
+% Discard

 %
 %

-\membersection{wxSocketBase::ReadMsg}\label{wxsocketbasereadmsg}
+\membersection{wxSocketBase::Discard}\label{wxsocketbasediscard}

 
 

-\func{wxSocketBase\&}{ReadMsg}{\param{char *}{ buffer}, \param{size\_t}{ nbytes}}
+\func{wxSocketBase\&}{Discard}{\void}

 
 

-This function reads a buffer sent by WriteMsg on a socket. If the buffer passed
-to the function isn't big enough, the function filled it and then discard the
-bytes left. This function always wait for the buffer to be entirely filled.
+This function simply deletes all bytes in the incoming queue. This function
+always returns immediately and its operation is not affected by IO flags.

 
 

-\wxheading{Parameters}
+Use \helpref{LastCount}{wxsocketbaselastcount} to verify the number of bytes actually discarded.

 
 

-\docparam{buffer}{Buffer where to put read data.}
+If you use \helpref{Error}{wxsocketbaseerror}, it will always return false.

 
 

-\docparam{nbytes}{Number of bytes allocated for the buffer.}
+%
+% Error
+%
+\membersection{wxSocketBase::Error}\label{wxsocketbaseerror}

 
 

-\wxheading{Return value}
+\constfunc{bool}{Error}{\void}

 
 

-Returns a reference to the current object.
+Returns true if an error occurred in the last IO operation.

 
 

-\wxheading{See also}
-
-\helpref{wxSocketBase::Error}{wxsocketbaseerror}\\
-\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}\\
-\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}\\
-\helpref{wxSocketBase::WriteMsg}{wxsocketbasewritemsg}
+Use this function to check for an error condition after one of the
+following calls: Discard, Peek, Read, ReadMsg, Unread, Write, WriteMsg.

 
 %
 
 %

-% Unread
+% GetClientData

 %
 %

-\membersection{wxSocketBase::UnRead}\label{wxsocketbaseunread}
+\membersection{wxSocketBase::GetClientData}\label{wxsocketbasegetclientdata}

 
 

-\func{wxSocketBase\&}{UnRead}{\param{const char *}{ buffer}, \param{size\_t}{ nbytes}}
+\constfunc{void *}{GetClientData}{\void}

 
 

-This function unreads a buffer. It means that the buffer is put in the top
-of the incoming queue. But, it is put also at the end of all unread buffers.
-It is useful for sockets because we can't seek it.
+Returns a pointer of the client data for this socket, as set with 
+\helpref{SetClientData}{wxsocketbasesetclientdata}

 
 

-\wxheading{Parameters}
+%
+% GetLocal
+%
+\membersection{wxSocketBase::GetLocal}\label{wxsocketbasegetlocal}

 
 

-\docparam{buffer}{Buffer to be unread.}
+\constfunc{bool}{GetLocal}{\param{wxSockAddress\& }{addr}}

 
 

-\docparam{nbytes}{Number of bytes.}
+This function returns the local address field of the socket. The local
+address field contains the complete local address of the socket (local
+address, local port, ...).

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns a reference to the current object.
-
-\wxheading{See also}
-
-\helpref{wxSocketBase::Error}{wxsocketbaseerror}\\
-\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}\\
-\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}
+true if no error happened, false otherwise.

 
 %
 
 %

-% Discard
+% GetFlags

 %
 %

-\membersection{wxSocketBase::Discard}\label{wxsocketbasediscard}
+\membersection{wxSocketBase::GetFlags}\label{wxsocketbasegetflags}

 
 

-\func{wxSocketBase\&}{Discard}{\void}
+\constfunc{wxSocketFlags}{GetFlags}{\void}

 
 

-This function simply deletes all bytes in the incoming queue. This function
-doesn't wait.
-
-% ---------------------------------------------------------------------------
-% Wait functions
-% ---------------------------------------------------------------------------
-\membersection{wxSocketBase::Wait}\label{wxsocketbasewait}
-
-\func{bool}{Wait}{\param{long}{ seconds = -1}, \param{long}{ microsecond = 0}}
-
-This function waits for an event: it could be an incoming byte, the possibility
-for the client to write, a lost connection, an incoming connection, an
-established connection.
+Returns current IO flags, as set with \helpref{SetFlags}{wxsocketbasesetflags}

 
 

-\wxheading{Parameters}
+%
+% GetPeer
+%
+\membersection{wxSocketBase::GetPeer}\label{wxsocketbasegetpeer}

 
 

-\docparam{seconds}{Number of seconds to wait. By default, it waits infinitely.}
+\constfunc{bool}{GetPeer}{\param{wxSockAddress\& }{addr}}

 
 

-\docparam{microsecond}{Number of microseconds to wait.}
+This function returns the peer address field of the socket. The peer 
+address field contains the complete peer host address of the socket
+(address, port, ...).

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns TRUE if an event occured, FALSE if the timeout was reached.
-
-\wxheading{See also}
-
-\helpref{wxSocketBase::WaitForRead}{wxsocketbasewaitforread}\\
-\helpref{wxSocketBase::WaitForWrite}{wxsocketbasewaitforwrite}\\
-\helpref{wxSocketBase::WaitForLost}{wxsocketbasewaitforlost}
+true if no error happened, false otherwise.

 
 %
 
 %

-% WaitForRead
+% InterruptWait

 %
 %

-\membersection{wxSocketBase::WaitForRead}\label{wxsocketbasewaitforread}
-
-\func{bool}{WaitForRead}{\param{long}{ seconds = -1}, \param{long}{ microsecond = 0}}
-
-This function waits for a read event.
+\membersection{wxSocketBase::InterruptWait}\label{wxsocketbaseinterruptwait}
+
+\func{void}{InterruptWait}{\void}
+
+Use this function to interrupt any wait operation currently in progress.
+Note that this is not intended as a regular way to interrupt a Wait call,
+but only as an escape mechanism for exceptional situations where it is
+absolutely necessary to use it, for example to abort an operation due to
+some exception or abnormal problem. InterruptWait is automatically called
+when you \helpref{Close}{wxsocketbaseclose} a socket (and thus also upon
+socket destruction), so you don't need to use it in these cases.
+
+\helpref{wxSocketBase::Wait}{wxsocketbasewait}, 
+\helpref{wxSocketServer::WaitForAccept}{wxsocketserverwaitforaccept}, 
+\helpref{wxSocketBase::WaitForLost}{wxsocketbasewaitforlost}, 
+\helpref{wxSocketBase::WaitForRead}{wxsocketbasewaitforread}, 
+\helpref{wxSocketBase::WaitForWrite}{wxsocketbasewaitforwrite}, 
+\helpref{wxSocketClient::WaitOnConnect}{wxsocketclientwaitonconnect}

 
 

-\wxheading{Parameters}
+%
+% IsConnected
+%
+\membersection{wxSocketBase::IsConnected}\label{wxsocketbaseisconnected}

 
 

-\docparam{seconds}{Number of seconds to wait. By default, it waits infinitely.}
+\constfunc{bool}{IsConnected}{\void}

 
 

-\docparam{microsecond}{Number of microseconds to wait.}
+Returns true if the socket is connected.

 
 

-\wxheading{Return value}
+%
+% IsData
+%
+\membersection{wxSocketBase::IsData}\label{wxsocketbaseisdata}

 
 

-Returns TRUE if a byte arrived, FALSE if the timeout was reached.
+\constfunc{bool}{IsData}{\void}

 
 

-\wxheading{See also}
+This function waits until the socket is readable. This might mean that
+queued data is available for reading or, for streamed sockets, that
+the connection has been closed, so that a read operation will complete
+immediately without blocking (unless the {\bf wxSOCKET\_WAITALL} flag
+is set, in which case the operation might still block).

 
 

-\helpref{wxSocketBase::Wait}{wxsocketbasewait}\\
-\helpref{wxSocketBase::WaitForWrite}{wxsocketbasewaitforwrite}\\
-\helpref{wxSocketBase::WaitForLost}{wxsocketbasewaitforlost}
+\membersection{wxSocketBase::IsDisconnected}\label{wxsocketbaseisdisconnected}

 
 %
 
 %

-% WaitForWrite
+% IsDisconnected

 %
 %

-\membersection{wxSocketBase::WaitForWrite}\label{wxsocketbasewaitforwrite}
+\constfunc{bool}{IsDisconnected}{\void}

 
 

-\func{bool}{WaitForWrite}{\param{long}{ seconds = -1}, \param{long}{ microsecond = 0}}
+Returns true if the socket is not connected.

 
 

-This function waits for a write event.
+\membersection{wxSocketBase::LastCount}\label{wxsocketbaselastcount}

 
 

-\wxheading{Parameters}
+%
+% LastCount
+%
+\constfunc{wxUint32}{LastCount}{\void}

 
 

-\docparam{seconds}{Number of seconds to wait. By default, it waits infinitely.}
+Returns the number of bytes read or written by the last IO call.

 
 

-\docparam{microsecond}{Number of microseconds to wait.}
+Use this function to get the number of bytes actually transferred
+after using one of the following IO calls: Discard, Peek, Read,
+ReadMsg, Unread, Write, WriteMsg.

 
 

-\wxheading{Return value}
+%
+% LastError
+%
+\membersection{wxSocketBase::LastError}\label{wxsocketbaselasterror}

 
 

-Returns TRUE if a write event occured, FALSE if the timeout was reached.
+\constfunc{wxSocketError}{LastError}{\void}

 
 

-\wxheading{See also}
+Returns the last wxSocket error. See \helpref{wxSocket errors}{wxsocketbase}.

 
 

-\helpref{wxSocketBase::Wait}{wxsocketbasewait}\\
-\helpref{wxSocketBase::WaitForRead}{wxsocketbasewaitforread}\\
-\helpref{wxSocketBase::WaitForLost}{wxsocketbasewaitforlost}
+Please note that this function merely returns the last error code,
+but it should not be used to determine if an error has occurred (this
+is because successful operations do not change the LastError value).
+Use \helpref{Error}{wxsocketbaseerror} first, in order to determine
+if the last IO call failed. If this returns true, use LastError
+to discover the cause of the error.

 
 %
 
 %

-% WaitForLost
+% Notify

 %
 %

-\membersection{wxSocketBase::WaitForLost}\label{wxsocketbasewaitforlost}
+\membersection{wxSocketBase::Notify}\label{wxsocketbasenotify}

 
 

-\func{bool}{Wait}{\param{long}{ seconds = -1}, \param{long}{ microsecond = 0}}
+\func{void}{Notify}{\param{bool}{ notify}}

 
 

-This function waits for a "lost" event. For instance, the peer may have closed
-the connection, or the connection may have been broken.
+According to the {\it notify} value, this function enables
+or disables socket events. If {\it notify} is true, the events
+configured with \helpref{SetNotify}{wxsocketbasesetnotify} will
+be sent to the application. If {\it notify} is false; no events
+will be sent.

 
 

-\wxheading{Parameters}
+% 
+% Ok
+%
+\membersection{wxSocketBase::Ok}\label{wxsocketbaseok}

 
 

-\docparam{seconds}{Number of seconds to wait. By default, it waits infinitely.}
+\constfunc{bool}{Ok}{\void}

 
 

-\docparam{microsecond}{Number of microseconds to wait.}
+Returns true if the socket is initialized and ready and false in other
+cases.

 
 

-\wxheading{Return value}
+\wxheading{Remark/Warning}

 
 

-Returns TRUE if a "lost" event occured, FALSE if the timeout was reached.
+For \helpref{wxSocketClient}{wxsocketclient}, Ok won't return true unless
+the client is connected to a server.

 
 

-\wxheading{See also}
+For \helpref{wxSocketServer}{wxsocketserver}, Ok will return true if the
+server could bind to the specified address and is already listening for
+new connections.

 
 

-\helpref{wxSocketBase::WaitForRead}{wxsocketbasewaitforread}\\
-\helpref{wxSocketBase::WaitForWrite}{wxsocketbasewaitforwrite}\\
-\helpref{wxSocketBase::WaitForLost}{wxsocketbasewaitforlost}
+Ok does not check for IO errors;
+use \helpref{Error}{wxsocketbaseerror} instead for that purpose.

 
 %
 % RestoreState
 
 %
 % RestoreState


@@ -418,15 +503,15 @@ Returns TRUE if a "lost" event occured, FALSE if the timeout was reached.
 
 \func{void}{RestoreState}{\void}
 
 
 \func{void}{RestoreState}{\void}
 

-This function restores a previously saved state.
+This function restores the previous state of the socket, as saved
+with \helpref{SaveState}{wxsocketbasesavestate}
+
+Calls to SaveState and RestoreState can be nested.

 
 \wxheading{See also}
 
 \helpref{wxSocketBase::SaveState}{wxsocketbasesavestate}
 
 
 \wxheading{See also}
 
 \helpref{wxSocketBase::SaveState}{wxsocketbasesavestate}
 

-% ---------------------------------------------------------------------------
-% Socket state
-% ---------------------------------------------------------------------------

 %
 % SaveState
 %
 %
 % SaveState
 %


@@ -434,369 +519,702 @@ This function restores a previously saved state.
 
 \func{void}{SaveState}{\void}
 
 
 \func{void}{SaveState}{\void}
 

-This function saves the current state of the socket object in a stack:
-actually it saves all flags and the state of the asynchronous callbacks. 
+This function saves the current state of the socket in a stack. Socket
+state includes flags, as set with \helpref{SetFlags}{wxsocketbasesetflags},
+event mask, as set with \helpref{SetNotify}{wxsocketbasesetnotify} and 
+\helpref{Notify}{wxsocketbasenotify}, user data, as set with 
+\helpref{SetClientData}{wxsocketbasesetclientdata}, and asynchronous
+callback settings, as set with \helpref{Callback}{wxsocketbasecallback} 
+and \helpref{CallbackData}{wxsocketbasecallbackdata}.
+
+Calls to SaveState and RestoreState can be nested.

 
 \wxheading{See also}
 
 \helpref{wxSocketBase::RestoreState}{wxsocketbaserestorestate}
 
 
 \wxheading{See also}
 
 \helpref{wxSocketBase::RestoreState}{wxsocketbaserestorestate}
 

-% ---------------------------------------------------------------------------
-% Socket callbacks
-% ---------------------------------------------------------------------------
+%
+% SetClientData
+%
+\membersection{wxSocketBase::SetClientData}\label{wxsocketbasesetclientdata}
+
+\func{void}{SetClientData}{\param{void *}{data}}
+
+Sets user-supplied client data for this socket. All socket events will
+contain a pointer to this data, which can be retrieved with
+the \helpref{wxSocketEvent::GetClientData}{wxsocketeventgetclientdata} function.
+
+%
+% SetEventHandler
+%

 \membersection{wxSocketBase::SetEventHandler}\label{wxsocketbaseseteventhandler}
 
 \membersection{wxSocketBase::SetEventHandler}\label{wxsocketbaseseteventhandler}
 

-\func{void}{SetEventHandler}{\param{wxEvtHandler\&}{ evt\_hdlr}, \param{int}{ id = -1}}
+\func{void}{SetEventHandler}{\param{wxEvtHandler\&}{ handler}, \param{int}{ id = -1}}

 
 

-Sets an event handler to be called when a socket event occured.
+Sets an event handler to be called when a socket event occurs. The
+handler will be called for those events for which notification is
+enabled with \helpref{SetNotify}{wxsocketbasesetnotify} and 
+\helpref{Notify}{wxsocketbasenotify}.

 
 \wxheading{Parameters}
 
 
 \wxheading{Parameters}
 

-\docparam{evt\_hdlr}{Specifies the event handler you want to use.}
+\docparam{handler}{Specifies the event handler you want to use.}

 
 \docparam{id}{The id of socket event.}
 
 \wxheading{See also}
 
 
 \docparam{id}{The id of socket event.}
 
 \wxheading{See also}
 

-\helpref{wxSocketEvent}{wxsocketevent}
+\helpref{wxSocketBase::SetNotify}{wxsocketbasesetnotify}, 
+\helpref{wxSocketBase::Notify}{wxsocketbasenotify}, 
+\helpref{wxSocketEvent}{wxsocketevent}, 
+\helpref{wxEvtHandler}{wxevthandler}

 
 

-% ---------------------------------------------------------------------------
-% CLASS wxSocketClient
-% ---------------------------------------------------------------------------
-\section{\class{wxSocketClient}}\label{wxsocketclient}
+%
+% SetFlags
+%
+\membersection{wxSocketBase::SetFlags}\label{wxsocketbasesetflags}

 
 

-\wxheading{Derived from}
+\func{void}{SetFlags}{\param{wxSocketFlags}{ flags}}

 
 

-\helpref{wxSocketBase}{wxsocketbase}
+Use SetFlags to customize IO operation for this socket.
+The {\it flags} parameter may be a combination of flags ORed together.
+The following flags can be used:
+
+\twocolwidtha{7cm}
+\begin{twocollist}\itemsep=0pt
+\twocolitem{{\bf wxSOCKET\_NONE}}{Normal functionality.}
+\twocolitem{{\bf wxSOCKET\_NOWAIT}}{Read/write as much data as possible and return immediately.}
+\twocolitem{{\bf wxSOCKET\_WAITALL}}{Wait for all required data to be read/written unless an error occurs.}
+\twocolitem{{\bf wxSOCKET\_BLOCK}}{Block the GUI (do not yield) while reading/writing data.}
+\end{twocollist}
+
+A brief overview on how to use these flags follows.
+
+If no flag is specified (this is the same as {\bf wxSOCKET\_NONE}),
+IO calls will return after some data has been read or written, even
+when the transfer might not be complete. This is the same as issuing
+exactly one blocking low-level call to recv() or send(). Note
+that {\it blocking} here refers to when the function returns, not
+to whether the GUI blocks during this time.
+
+If {\bf wxSOCKET\_NOWAIT} is specified, IO calls will return immediately.
+Read operations will retrieve only available data. Write operations will
+write as much data as possible, depending on how much space is available
+in the output buffer. This is the same as issuing exactly one nonblocking
+low-level call to recv() or send(). Note that {\it nonblocking} here
+refers to when the function returns, not to whether the GUI blocks during
+this time.
+
+If {\bf wxSOCKET\_WAITALL} is specified, IO calls won't return until ALL
+the data has been read or written (or until an error occurs), blocking if
+necessary, and issuing several low level calls if necessary. This is the
+same as having a loop which makes as many blocking low-level calls to
+recv() or send() as needed so as to transfer all the data. Note
+that {\it blocking} here refers to when the function returns, not
+to whether the GUI blocks during this time.
+
+The {\bf wxSOCKET\_BLOCK} flag controls whether the GUI blocks during
+IO operations. If this flag is specified, the socket will not yield
+during IO calls, so the GUI will remain blocked until the operation
+completes. If it is not used, then the application must take extra
+care to avoid unwanted reentrance.
+
+So:
+
+{\bf wxSOCKET\_NONE} will try to read at least SOME data, no matter how much.
+
+{\bf wxSOCKET\_NOWAIT} will always return immediately, even if it cannot
+read or write ANY data.
+
+{\bf wxSOCKET\_WAITALL} will only return when it has read or written ALL
+the data.
+
+{\bf wxSOCKET\_BLOCK} has nothing to do with the previous flags and
+it controls whether the GUI blocks.

 
 

-% ---------------------------------------------------------------------------
-% Members
-% ---------------------------------------------------------------------------

 %
 %

-% wxSocketClient
+% SetNotify

 %
 %

-\membersection{wxSocketClient::wxSocketClient}
+\membersection{wxSocketBase::SetNotify}\label{wxsocketbasesetnotify}

 
 

-\func{}{wxSocketClient}{\param{wxSockFlags}{ flags = wxSocketBase::NONE}}
+\func{void}{SetNotify}{\param{wxSocketEventFlags}{ flags}}

 
 

-Constructs a new wxSocketClient.
+SetNotify specifies which socket events are to be sent to the event handler.
+The {\it flags} parameter may be combination of flags ORed together. The
+following flags can be used:

 
 

-{\bf Warning !} The new socket client needs to be registered to a socket handler (See \helpref{wxSocketHandler}{wxsockethandler}).
+\twocolwidtha{7cm}
+\begin{twocollist}\itemsep=0pt
+\twocolitem{{\bf wxSOCKET\_INPUT\_FLAG}}{to receive wxSOCKET\_INPUT}
+\twocolitem{{\bf wxSOCKET\_OUTPUT\_FLAG}}{to receive wxSOCKET\_OUTPUT}
+\twocolitem{{\bf wxSOCKET\_CONNECTION\_FLAG}}{to receive wxSOCKET\_CONNECTION}
+\twocolitem{{\bf wxSOCKET\_LOST\_FLAG}}{to receive wxSOCKET\_LOST}
+\end{twocollist}

 
 

-\wxheading{Parameters}
+For example:

 
 

-\docparam{flags}{Socket flags (See \helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags})}
+\begin{verbatim}
+  sock.SetNotify(wxSOCKET_INPUT_FLAG | wxSOCKET_LOST_FLAG);
+  sock.Notify(true);
+\end{verbatim}
+
+In this example, the user will be notified about incoming socket data and
+whenever the connection is closed.
+
+For more information on socket events see \helpref{wxSocket events}{wxsocketbase}.

 
 %
 
 %

-% ~wxSocketClient
+% SetTimeout

 %
 %

-\membersection{wxSocketClient::\destruct{wxSocketClient}}
+\membersection{wxSocketBase::SetTimeout}\label{wxsocketbasesettimeout}

 
 

-\func{}{\destruct{wxSocketClient}}{\void}
+\func{void}{SetTimeout}{\param{int }{seconds}}

 
 

-Destroys a wxSocketClient object.
+This function sets the default socket timeout in seconds. This timeout
+applies to all IO calls, and also to the \helpref{Wait}{wxsocketbasewait} family
+of functions if you don't specify a wait interval. Initially, the default
+timeout is 10 minutes.

 
 %
 
 %

-% Connect
+% Peek

 %
 %

-\membersection{wxSocketClient::Connect}\label{wxsocketclientconnect}
+\membersection{wxSocketBase::Peek}\label{wxsocketbasepeek}
+
+\func{wxSocketBase\&}{Peek}{\param{void *}{ buffer}, \param{wxUint32}{ nbytes}}

 
 

-\func{bool}{Connect}{\param{wxSockAddress\&}{ address}, \param{bool}{ wait = TRUE}}
+This function peeks a buffer of {\it nbytes} bytes from the socket.
+Peeking a buffer doesn't delete it from the socket input queue.

 
 

-Connects to a server using the specified address. If {\it wait} is TRUE, Connect
-will wait for the socket ready to send or receive data.
+Use \helpref{LastCount}{wxsocketbaselastcount} to verify the number of bytes actually peeked.
+
+Use \helpref{Error}{wxsocketbaseerror} to determine if the operation succeeded.

 
 \wxheading{Parameters}
 
 
 \wxheading{Parameters}
 

-\docparam{address}{Address of the server.}
+\docparam{buffer}{Buffer where to put peeked data.}

 
 

-\docparam{wait}{If true, waits for the connection to be ready.}
+\docparam{nbytes}{Number of bytes.}

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns TRUE if the connection is established and no error occurs.
+Returns a reference to the current object.
+
+\wxheading{Remark/Warning}
+
+The exact behaviour of wxSocketBase::Peek depends on the combination
+of flags being used. For a detailed explanation, see \helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}

 
 \wxheading{See also}
 
 
 \wxheading{See also}
 

-\helpref{wxSocketClient::WaitOnConnect}{wxsocketclientwaitonconnect}
+\helpref{wxSocketBase::Error}{wxsocketbaseerror}, 
+\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}, 
+\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}, 
+\helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}

 
 %
 
 %

-% WaitOnConnect
+% Read

 %
 %

-\membersection{wxSocketClient::WaitOnConnect}\label{wxsocketclientwaitonconnect}
+\membersection{wxSocketBase::Read}\label{wxsocketbaseread}

 
 

-\func{bool}{WaitOnConnect}{\param{long}{ seconds = -1}, \param{long}{ microseconds = 0}}
+\func{wxSocketBase\&}{Read}{\param{void *}{ buffer}, \param{wxUint32}{ nbytes}}

 
 

-Wait for a "connect" event.
+This function reads a buffer of {\it nbytes} bytes from the socket.

 
 

-\wxheading{See also}
+Use \helpref{LastCount}{wxsocketbaselastcount} to verify the number of bytes actually read.

 
 

-\helpref{wxSocketBase::Wait}{wxsocketbasewait} for a detailed description.
+Use \helpref{Error}{wxsocketbaseerror} to determine if the operation succeeded.

 
 

-% ---------------------------------------------------------------------------
-% CLASS: wxSocketEvent
-% ---------------------------------------------------------------------------
-\section{\class{wxSocketEvent}}\label{wxsocketevent}
+\wxheading{Parameters}

 
 

-This event class contains information about socket events.
+\docparam{buffer}{Buffer where to put read data.}

 
 

-\wxheading{Derived from}
+\docparam{nbytes}{Number of bytes.}

 
 

-\helpref{wxEvent}{wxevent}
+\wxheading{Return value}

 
 

-\wxheading{Event table macros}
+Returns a reference to the current object.

 
 

-To process a socket event, use these event handler macros to direct input to member
-functions that take a wxSocketEvent argument.
+\wxheading{Remark/Warning}

 
 

-\twocolwidtha{7cm}
-\begin{twocollist}\itemsep=0pt
-\twocolitem{{\bf EVT\_SOCKET(id, func)}}{Process a socket event, supplying the member function.}
-\end{twocollist}%
+The exact behaviour of wxSocketBase::Read depends on the combination
+of flags being used. For a detailed explanation, see \helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}.

 
 \wxheading{See also}
 
 
 \wxheading{See also}
 

-\helpref{wxSocketHandler}{wxsockethandler},\rtfsp
-\helpref{wxSocketBase}{wxsocketbase},\rtfsp
-\helpref{wxSocketClient}{wxsocketclient},\rtfsp
-\helpref{wxSocketServer}{wxsocketserver}
+\helpref{wxSocketBase::Error}{wxsocketbaseerror}, 
+\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}, 
+\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}, 
+\helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}

 
 

-\latexignore{\rtfignore{\wxheading{Members}}}
+%
+% ReadMsg
+%
+\membersection{wxSocketBase::ReadMsg}\label{wxsocketbasereadmsg}

 
 

-\membersection{wxSocketEvent::wxSocketEvent}
+\func{wxSocketBase\&}{ReadMsg}{\param{void *}{ buffer}, \param{wxUint32}{ nbytes}}

 
 

-\func{}{wxSocketEvent}{\param{int}{ id = 0}}
+This function reads a buffer sent by \helpref{WriteMsg}{wxsocketbasewritemsg} 
+on a socket. If the buffer passed to the function isn't big enough, the
+remaining bytes will be discarded. This function always waits for the
+buffer to be entirely filled, unless an error occurs.

 
 

-Constructor.
+Use \helpref{LastCount}{wxsocketbaselastcount} to verify the number of bytes actually read.

 
 

-\membersection{wxSocketEvent::SocketEvent}\label{wxsocketeventsocketevent}
+Use \helpref{Error}{wxsocketbaseerror} to determine if the operation succeeded.

 
 

-\constfunc{wxSocketBase::wxRequestEvent}{SocketEvent}{\void}
+\wxheading{Parameters}

 
 

-Returns the socket event type.
+\docparam{buffer}{Buffer where to put read data.}

 
 

-% ---------------------------------------------------------------------------
-% CLASS: wxSocketHandler
-% ---------------------------------------------------------------------------
-\section{\class{wxSocketHandler}}\label{wxsockethandler}
+\docparam{nbytes}{Size of the buffer.}

 
 

-\wxheading{Derived from}
+\wxheading{Return value}

 
 

-\helpref{wxObject}{wxobject}
+Returns a reference to the current object.

 
 

-% ---------------------------------------------------------------------------
-% Members
-% ---------------------------------------------------------------------------
-\latexignore{\rtfignore{\wxheading{Members}}}
+\wxheading{Remark/Warning}
+
+wxSocketBase::ReadMsg will behave as if the {\bf wxSOCKET\_WAITALL} flag
+was always set and it will always ignore the {\bf wxSOCKET\_NOWAIT} flag.
+The exact behaviour of ReadMsg depends on the {\bf wxSOCKET\_BLOCK} flag.
+For a detailed explanation, see \helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}.
+
+\wxheading{See also}
+
+\helpref{wxSocketBase::Error}{wxsocketbaseerror}, 
+\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}, 
+\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}, 
+\helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}, 
+\helpref{wxSocketBase::WriteMsg}{wxsocketbasewritemsg}

 
 %
 
 %

-% wxSocketHandler
+% Unread

 %
 %

-\membersection{wxSocketHandler::wxSocketHandler}
+\membersection{wxSocketBase::Unread}\label{wxsocketbaseunread}

 
 

-\func{}{wxSocketHandler}{\void}
+\func{wxSocketBase\&}{Unread}{\param{const void *}{ buffer}, \param{wxUint32}{ nbytes}}

 
 

-Constructs a new wxSocketHandler.
+This function unreads a buffer. That is, the data in the buffer is put back
+in the incoming queue. This function is not affected by wxSocket flags.

 
 

-It is advised to use \helpref{wxSocketHandler::Master}{wxsockethandlermaster} to
-get a socket handler. But creating a socket handler is useful to group
-many sockets.
+If you use \helpref{LastCount}{wxsocketbaselastcount}, it will always return {\it nbytes}.

 
 

-%
-% ~wxSocketHandler
-%
-\membersection{wxSocketHandler::\destruct{wxSocketHandler}}
+If you use \helpref{Error}{wxsocketbaseerror}, it will always return false.

 
 

-\func{}{\destruct{wxSocketHandler}}{\void}
+\wxheading{Parameters}

 
 

-Destroys a wxSocketHandler object.
+\docparam{buffer}{Buffer to be unread.}
+
+\docparam{nbytes}{Number of bytes.}
+
+\wxheading{Return value}
+
+Returns a reference to the current object.
+
+\wxheading{See also}
+
+\helpref{wxSocketBase::Error}{wxsocketbaseerror}, 
+\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}, 
+\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}

 
 %
 
 %

-% Register
+% Wait

 %
 %

-\membersection{wxSocketHandler::Register}
+\membersection{wxSocketBase::Wait}\label{wxsocketbasewait}
+
+\func{bool}{Wait}{\param{long}{ seconds = -1}, \param{long}{ millisecond = 0}}

 
 

-\func{void}{Register}{\param{wxSocketBase *}{socket}}
+This function waits until any of the following conditions is true:
+                                            
+\begin{itemize}
+\item The socket becomes readable.
+\item The socket becomes writable.
+\item An ongoing connection request has completed (\helpref{wxSocketClient}{wxsocketclient} only)
+\item An incoming connection request has arrived (\helpref{wxSocketServer}{wxsocketserver} only)
+\item The connection has been closed.
+\end{itemize}

 
 

-Register a socket: if it is already registered in this handler it will just
-return immediately.
+Note that it is recommended to use the individual Wait functions
+to wait for the required condition, instead of this one.

 
 \wxheading{Parameters}
 
 
 \wxheading{Parameters}
 

-\docparam{socket}{Socket to be registered.}
+\docparam{seconds}{Number of seconds to wait.
+If -1, it will wait for the default timeout,
+as set with \helpref{SetTimeout}{wxsocketbasesettimeout}.}
+
+\docparam{millisecond}{Number of milliseconds to wait.}
+
+\wxheading{Return value}
+
+Returns true when any of the above conditions is satisfied,
+false if the timeout was reached.
+
+\wxheading{See also}
+
+\helpref{wxSocketBase::InterruptWait}{wxsocketbaseinterruptwait}, 
+\helpref{wxSocketServer::WaitForAccept}{wxsocketserverwaitforaccept}, 
+\helpref{wxSocketBase::WaitForLost}{wxsocketbasewaitforlost}, 
+\helpref{wxSocketBase::WaitForRead}{wxsocketbasewaitforread}, 
+\helpref{wxSocketBase::WaitForWrite}{wxsocketbasewaitforwrite}, 
+\helpref{wxSocketClient::WaitOnConnect}{wxsocketclientwaitonconnect}

 
 %
 
 %

-% UnRegister
+% WaitForLost

 %
 %

-\membersection{wxSocketHandler::UnRegister}
+\membersection{wxSocketBase::WaitForLost}\label{wxsocketbasewaitforlost}

 
 

-\func{void}{UnRegister}{\param{wxSocketBase *}{socket}}
+\func{bool}{Wait}{\param{long}{ seconds = -1}, \param{long}{ millisecond = 0}}

 
 

-UnRegister a socket: if it isn't registered in this handler it will just
-return.
+This function waits until the connection is lost. This may happen if
+the peer gracefully closes the connection or if the connection breaks.

 
 \wxheading{Parameters}
 
 
 \wxheading{Parameters}
 

-\docparam{socket}{Socket to be unregistered.}
+\docparam{seconds}{Number of seconds to wait.
+If -1, it will wait for the default timeout,
+as set with \helpref{SetTimeout}{wxsocketbasesettimeout}.}
+
+\docparam{millisecond}{Number of milliseconds to wait.}
+
+\wxheading{Return value}
+
+Returns true if the connection was lost, false if the timeout was reached.
+
+\wxheading{See also}
+
+\helpref{wxSocketBase::InterruptWait}{wxsocketbaseinterruptwait},
+\helpref{wxSocketBase::Wait}{wxsocketbasewait}

 
 %
 
 %

-% Count
+% WaitForRead

 %
 %

-\membersection{wxSocketHandler::Count}
+\membersection{wxSocketBase::WaitForRead}\label{wxsocketbasewaitforread}
+
+\func{bool}{WaitForRead}{\param{long}{ seconds = -1}, \param{long}{ millisecond = 0}}
+
+This function waits until the socket is readable. This might mean that
+queued data is available for reading or, for streamed sockets, that
+the connection has been closed, so that a read operation will complete
+immediately without blocking (unless the {\bf wxSOCKET\_WAITALL} flag
+is set, in which case the operation might still block).
+
+\wxheading{Parameters}

 
 

-\constfunc{unsigned long}{Count}{\void}
+\docparam{seconds}{Number of seconds to wait.
+If -1, it will wait for the default timeout,
+as set with \helpref{SetTimeout}{wxsocketbasesettimeout}.}

 
 

-Returns the number of sockets registered in the handler.
+\docparam{millisecond}{Number of milliseconds to wait.}

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Number of sockets registered.
+Returns true if the socket becomes readable, false on timeout.
+
+\wxheading{See also}
+
+\helpref{wxSocketBase::InterruptWait}{wxsocketbaseinterruptwait}, 
+\helpref{wxSocketBase::Wait}{wxsocketbasewait}

 
 %
 
 %

-% CreateServer
+% WaitForWrite

 %
 %

-\membersection{wxSocketHandler::CreateServer}
+\membersection{wxSocketBase::WaitForWrite}\label{wxsocketbasewaitforwrite}

 
 

-\func{wxSocketServer *}{CreateServer}{\param{wxSockAddress\&}{ address}, \param{wxSocketBase::wxSockFlags}{ flags = wxSocketbase::NONE}}
+\func{bool}{WaitForWrite}{\param{long}{ seconds = -1}, \param{long}{ millisecond = 0}}

 
 

-Creates a new wxSocketServer object. The object is automatically registered
-to the current socket handler.
-For a detailed description of the parameters, see \helpref{wxSocketServer::wxSocketServer}{wxsocketserverconstr}.
+This function waits until the socket becomes writable. This might mean that
+the socket is ready to send new data, or for streamed sockets, that the
+connection has been closed, so that a write operation is guaranteed to
+complete immediately (unless the {\bf wxSOCKET\_WAITALL} flag is set,
+in which case the operation might still block).
+
+\wxheading{Parameters}
+
+\docparam{seconds}{Number of seconds to wait.
+If -1, it will wait for the default timeout,
+as set with \helpref{SetTimeout}{wxsocketbasesettimeout}.}
+
+\docparam{millisecond}{Number of milliseconds to wait.}

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns a new socket server.
+Returns true if the socket becomes writable, false on timeout.
+
+\wxheading{See also}
+
+\helpref{wxSocketBase::InterruptWait}{wxsocketbaseinterruptwait}, 
+\helpref{wxSocketBase::Wait}{wxsocketbasewait}

 
 %
 
 %

-% CreateClient
+% Write

 %
 %

-\membersection{wxSocketHandler::CreateClient}
+\membersection{wxSocketBase::Write}\label{wxsocketbasewrite}
+
+\func{wxSocketBase\&}{Write}{\param{const void *}{ buffer}, \param{wxUint32}{ nbytes}}

 
 

-\func{wxSocketServer *}{CreateClient}{\param{wxSocketBase::wxSockFlags}{ flags = wxSocketbase::NONE}}
+This function writes a buffer of {\it nbytes} bytes to the socket.

 
 

-Creates a new wxSocketClient object. The object is automatically registered
-to the current socket handler.
+Use \helpref{LastCount}{wxsocketbaselastcount} to verify the number of bytes actually written.

 
 

-For a detailed description of the parameters, see \helpref{wxSocketClient::Connect}{wxsocketclientconnect}.
+Use \helpref{Error}{wxsocketbaseerror} to determine if the operation succeeded.
+
+\wxheading{Parameters}
+
+\docparam{buffer}{Buffer with the data to be sent.}
+
+\docparam{nbytes}{Number of bytes.}

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns a new socket client.
+Returns a reference to the current object.

 
 

-%
-% Master
-%
-\membersection{wxSocketHandler::Master}\label{wxsockethandlermaster}
+\wxheading{Remark/Warning}

 
 

-\func{static wxSocketHandler\&}{Master}{\void}
+The exact behaviour of wxSocketBase::Write depends on the combination
+of flags being used. For a detailed explanation, see \helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}.

 
 

-Returns a default socket handler.
+\wxheading{See also}
+
+\helpref{wxSocketBase::Error}{wxsocketbaseerror}, 
+\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}, 
+\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}, 
+\helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}

 
 %
 
 %

-% Wait
+% WriteMsg

 %
 %

-\membersection{wxSocketHandler::Wait}
+\membersection{wxSocketBase::WriteMsg}\label{wxsocketbasewritemsg}
+
+\func{wxSocketBase\&}{WriteMsg}{\param{const void *}{ buffer}, \param{wxUint32}{ nbytes}}
+
+This function writes a buffer of {\it nbytes} bytes from the socket, but it
+writes a short header before so that \helpref{ReadMsg}{wxsocketbasereadmsg} 
+knows how much data should it actually read. So, a buffer sent with WriteMsg 
+{\bf must} be read with ReadMsg. This function always waits for the entire
+buffer to be sent, unless an error occurs.

 
 

-\func{int}{Wait}{\param{long}{ seconds},\param{long}{ microseconds}}
+Use \helpref{LastCount}{wxsocketbaselastcount} to verify the number of bytes actually written.

 
 

-Wait for an event on all registered sockets.
+Use \helpref{Error}{wxsocketbaseerror} to determine if the operation succeeded.

 
 \wxheading{Parameters}
 
 
 \wxheading{Parameters}
 

-\docparam{seconds}{Number of seconds to wait. By default, it waits infinitely.}
+\docparam{buffer}{Buffer with the data to be sent.}

 
 

-\docparam{microsecond}{Number of microseconds to wait.}
+\docparam{nbytes}{Number of bytes to send.}

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns 0 if a timeout occured, else the number of events detected.
+Returns a reference to the current object.

 
 

-\wxheading{See also}
+\wxheading{Remark/Warning}

 
 

-\helpref{wxSocketBase::Wait}{wxsocketbasewait}
+wxSocketBase::WriteMsg will behave as if the {\bf wxSOCKET\_WAITALL} flag
+was always set and it will always ignore the {\bf wxSOCKET\_NOWAIT} flag.
+The exact behaviour of WriteMsg depends on the {\bf wxSOCKET\_BLOCK} flag.
+For a detailed explanation, see \helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}.

 
 

-%
-% YieldSock
-%
-\membersection{wxSocketHandler::YieldSock}
+\wxheading{See also}

 
 

-\func{void}{YieldSock}{\void}
+\helpref{wxSocketBase::Error}{wxsocketbaseerror}, 
+\helpref{wxSocketBase::LastError}{wxsocketbaselasterror}, 
+\helpref{wxSocketBase::LastCount}{wxsocketbaselastcount}, 
+\helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags}, 
+\helpref{wxSocketBase::ReadMsg}{wxsocketbasereadmsg}

 
 

-Execute pending requests in all registered sockets.

 
 % ---------------------------------------------------------------------------
 
 % ---------------------------------------------------------------------------

-% CLASS: wxSocketServer
+% CLASS wxSocketClient

 % ---------------------------------------------------------------------------
 % ---------------------------------------------------------------------------

-\section{\class{wxSocketServer}}\label{wxsocketserver}
+
+\section{\class{wxSocketClient}}\label{wxsocketclient}

 
 \wxheading{Derived from}
 
 \helpref{wxSocketBase}{wxsocketbase}
 
 
 \wxheading{Derived from}
 
 \helpref{wxSocketBase}{wxsocketbase}
 

+\wxheading{Include files}
+
+<wx/socket.h>
+
+\latexignore{\rtfignore{\wxheading{Members}}}
+

 % ---------------------------------------------------------------------------
 % Members
 % ---------------------------------------------------------------------------
 % ---------------------------------------------------------------------------
 % Members
 % ---------------------------------------------------------------------------

-\latexignore{\rtfignore{\wxheading{Members}}}
-

 %
 %

-% wxSocketServer
+% wxSocketClient

 %
 %

-\membersection{wxSocketServer::wxSocketServer}\label{wxsocketserverconstr}
-
-\func{}{wxSocketServer}{\param{wxSockAddress\&}{ address}, \param{wxSockFlags}{ flags = wxSocketBase::NONE}}
+\membersection{wxSocketClient::wxSocketClient}

 
 

-Constructs a new wxSocketServer.
+\func{}{wxSocketClient}{\param{wxSocketFlags}{ flags = wxSOCKET\_NONE}}

 
 

-{\bf Warning !} The created object needs to be registered to a socket handler
-(see \helpref{wxSocketHandler}{wxsockethandler}).
+Constructor.

 
 \wxheading{Parameters}
 
 
 \wxheading{Parameters}
 

-\docparam{address}{Specifies the local address for the server (e.g. port number).}
-

 \docparam{flags}{Socket flags (See \helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags})}
 
 %
 \docparam{flags}{Socket flags (See \helpref{wxSocketBase::SetFlags}{wxsocketbasesetflags})}
 
 %

-% ~wxSocketServer
+% ~wxSocketClient

 %
 %

-\membersection{wxSocketServer::\destruct{wxSocketServer}}
+\membersection{wxSocketClient::\destruct{wxSocketClient}}

 
 

-\func{}{\destruct{wxSocketServer}}{\void}
+\func{}{\destruct{wxSocketClient}}{\void}

 
 

-Destroys a wxSocketServer object (it doesn't close the accepted connection).
+Destructor. Please see \helpref{wxSocketBase::Destroy}{wxsocketbasedestroy}.

 
 %
 
 %

-% Accept
+% Connect

 %
 %

-\membersection{wxSocketServer::Accept}
+\membersection{wxSocketClient::Connect}\label{wxsocketclientconnect}
+
+\func{bool}{Connect}{\param{wxSockAddress\&}{ address}, \param{bool}{ wait = true}}
+
+Connects to a server using the specified address.

 
 

-\func{wxSocketBase *}{Accept}{\void}
+If {\it wait} is true, Connect will wait until the connection
+completes. {\bf Warning:} This will block the GUI.

 
 

-Creates a new object wxSocketBase and accepts an incoming connection. {\bf Warning !} This function will block the GUI.
+If {\it wait} is false, Connect will try to establish the connection and
+return immediately, without blocking the GUI. When used this way, even if
+Connect returns false, the connection request can be completed later.
+To detect this, use \helpref{WaitOnConnect}{wxsocketclientwaitonconnect},
+or catch {\bf wxSOCKET\_CONNECTION} events (for successful establishment)
+and {\bf wxSOCKET\_LOST} events (for connection failure).
+
+\wxheading{Parameters}
+
+\docparam{address}{Address of the server.}
+
+\docparam{wait}{If true, waits for the connection to complete.}

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns an opened socket connection.
+Returns true if the connection is established and no error occurs.
+
+If {\it wait} was true, and Connect returns false, an error occurred
+and the connection failed.
+
+If {\it wait} was false, and Connect returns false, you should still
+be prepared to handle the completion of this connection request, either
+with \helpref{WaitOnConnect}{wxsocketclientwaitonconnect} or by
+watching {\bf wxSOCKET\_CONNECTION} and {\bf wxSOCKET\_LOST} events.

 
 \wxheading{See also}
 
 
 \wxheading{See also}
 

-\helpref{wxSocketServer::AcceptWith}{wxsocketserveracceptwith}
+\helpref{wxSocketClient::WaitOnConnect}{wxsocketclientwaitonconnect}, 
+\helpref{wxSocketBase::SetNotify}{wxsocketbasesetnotify}, 
+\helpref{wxSocketBase::Notify}{wxsocketbasenotify}

 
 %
 
 %

-% AcceptWith
+% WaitOnConnect

 %
 %

-\membersection{wxSocketServer::AcceptWith}\label{wxsocketserveracceptwith}
+\membersection{wxSocketClient::WaitOnConnect}\label{wxsocketclientwaitonconnect}

 
 

-\func{bool}{AcceptWith}{\param{wxSocketBase\&}{ socket}}
+\func{bool}{WaitOnConnect}{\param{long}{ seconds = -1}, \param{long}{ milliseconds = 0}}

 
 

-Accept an incoming connection using the specified socket object.
-This is useful when someone wants to inherit wxSocketBase.
+Wait until a connection request completes, or until the specified timeout
+elapses. Use this function after issuing a call
+to \helpref{Connect}{wxsocketclientconnect} with {\it wait} set to false.

 
 \wxheading{Parameters}
 
 
 \wxheading{Parameters}
 

-\docparam{socket}{Socket to be initialized}
+\docparam{seconds}{Number of seconds to wait.
+If -1, it will wait for the default timeout,
+as set with \helpref{SetTimeout}{wxsocketbasesettimeout}.}
+
+\docparam{millisecond}{Number of milliseconds to wait.}

 
 \wxheading{Return value}
 
 
 \wxheading{Return value}
 

-Returns TRUE if no error occurs, else FALSE.
+WaitOnConnect returns true if the connection request completes. This
+does not necessarily mean that the connection was successfully established;
+it might also happen that the connection was refused by the peer. Use 
+\helpref{IsConnected}{wxsocketbaseisconnected} to distinguish between
+these two situations.
+
+If the timeout elapses, WaitOnConnect returns false.
+
+These semantics allow code like this:
+
+\begin{verbatim}
+// Issue the connection request
+client->Connect(addr, false);
+
+// Wait until the request completes or until we decide to give up
+bool waitmore = true; 
+while ( !client->WaitOnConnect(seconds, millis) && waitmore )
+{
+    // possibly give some feedback to the user,
+    // and update waitmore as needed.
+}
+bool success = client->IsConnected();
+\end{verbatim}
+
+\wxheading{See also}
+
+\helpref{wxSocketClient::Connect}{wxsocketclientconnect}, 
+\helpref{wxSocketBase::InterruptWait}{wxsocketbaseinterruptwait}, 
+\helpref{wxSocketBase::IsConnected}{wxsocketbaseisconnected}
+
+% ---------------------------------------------------------------------------
+% CLASS: wxSocketEvent
+% ---------------------------------------------------------------------------
+\section{\class{wxSocketEvent}}\label{wxsocketevent}
+
+This event class contains information about socket events.
+
+\wxheading{Derived from}
+
+\helpref{wxEvent}{wxevent}
+
+\wxheading{Include files}
+
+<wx/socket.h>
+
+\wxheading{Event table macros}
+
+To process a socket event, use these event handler macros to direct input
+to member functions that take a wxSocketEvent argument.
+
+\twocolwidtha{7cm}
+\begin{twocollist}\itemsep=0pt
+\twocolitem{{\bf EVT\_SOCKET(id, func)}}{Process a socket event, supplying the member function.}
+\end{twocollist}
+
+\wxheading{See also}
+
+\helpref{wxSocketBase}{wxsocketbase}, 
+\helpref{wxSocketClient}{wxsocketclient}, 
+\helpref{wxSocketServer}{wxsocketserver}
+
+\latexignore{\rtfignore{\wxheading{Members}}}
+
+\membersection{wxSocketEvent::wxSocketEvent}
+
+\func{}{wxSocketEvent}{\param{int}{ id = 0}}
+
+Constructor.
+
+\membersection{wxSocketEvent::GetClientData}\label{wxsocketeventgetclientdata}
+
+\func{void *}{GetClientData}{\void}
+
+Gets the client data of the socket which generated this event, as
+set with \helpref{wxSocketBase::SetClientData}{wxsocketbasesetclientdata}.
+
+\membersection{wxSocketEvent::GetSocket}\label{wxsocketeventgetsocket}
+
+\constfunc{wxSocketBase *}{GetSocket}{\void}
+
+Returns the socket object to which this event refers to. This makes
+it possible to use the same event handler for different sockets.
+
+\membersection{wxSocketEvent::GetSocketEvent}\label{wxsocketeventgetsocketevent}
+
+\constfunc{wxSocketNotify}{GetSocketEvent}{\void}
+
+Returns the socket event type.