]>
git.saurik.com Git - wxWidgets.git/blob - interface/wx/socket.h
1 /////////////////////////////////////////////////////////////////////////////
3 // Purpose: interface of wxIP*address, wxSocket* classes
4 // Author: wxWidgets team
6 // Licence: wxWindows licence
7 /////////////////////////////////////////////////////////////////////////////
13 wxIPaddress is an abstract base class for all internet protocol address
14 objects. Currently, only wxIPV4address is implemented. An experimental
15 implementation for IPV6, wxIPV6address, is being developed.
20 class wxIPaddress
: public wxSockAddress
24 Internally, this is the same as setting the IP address to @b INADDR_ANY.
26 On IPV4 implementations, 0.0.0.0
28 On IPV6 implementations, ::
30 @return @true on success, @false if something went wrong.
35 Internally, this is the same as setting the IP address to @b INADDR_BROADCAST.
37 On IPV4 implementations, 255.255.255.255
39 @return @true on success, @false if something went wrong.
41 virtual bool BroadcastAddress() = 0;
44 Set the address to hostname, which can be a host name or an IP-style address
45 in a format dependent on implementation.
47 @return @true on success, @false if something goes wrong (invalid
48 hostname or invalid IP address).
50 bool Hostname(const wxString
& hostname
);
53 Returns the hostname which matches the IP address.
55 wxString
Hostname() const;
58 Returns a wxString containing the IP address.
60 virtual wxString
IPAddress() const = 0;
63 Determines if current address is set to localhost.
65 @return @true if address is localhost, @false if internet address.
67 virtual bool IsLocalHost() const = 0;
70 Set address to localhost.
72 On IPV4 implementations, 127.0.0.1
74 On IPV6 implementations, ::1
76 @return @true on success, @false if something went wrong.
81 Set the port to that corresponding to the specified service.
83 @return @true on success, @false if something goes wrong (invalid @a service).
85 bool Service(const wxString
& service
);
88 Set the port to that corresponding to the specified service.
90 @return @true on success, @false if something goes wrong (invalid @a service).
92 bool Service(unsigned short service
);
95 Returns the current service.
97 unsigned short Service() const;
104 A class for working with IPv4 network addresses.
109 class wxIPV4address
: public wxIPaddress
113 Set address to any of the addresses of the current machine.
115 Whenever possible, use this function instead of LocalHost(),
116 as this correctly handles multi-homed hosts and avoids other small
117 problems. Internally, this is the same as setting the IP address
120 @return @true on success, @false if something went wrong.
125 Set the address to hostname, which can be a host name or an IP-style address
126 in dot notation(<tt>a.b.c.d</tt>).
128 @return @true on success, @false if something goes wrong (invalid
129 hostname or invalid IP address).
131 bool Hostname(const wxString
& hostname
);
134 Returns the hostname which matches the IP address.
136 virtual wxString
Hostname() const;
139 Returns a wxString containing the IP address in dot quad (127.0.0.1) format.
141 virtual wxString
IPAddress() const;
144 Set address to localhost (127.0.0.1).
146 Whenever possible, use AnyAddress() instead of this one, as that one will
147 correctly handle multi-homed hosts and avoid other small problems.
149 @return @true on success, @false if something went wrong.
154 Set the port to that corresponding to the specified @a service.
156 @return @true on success, @false if something goes wrong (invalid @a service).
158 bool Service(const wxString
& service
);
161 Set the port to that corresponding to the specified @a service.
163 @return @true on success, @false if something goes wrong (invalid @a service).
165 bool Service(unsigned short service
);
168 Returns the current service.
170 unsigned short Service() const;
176 @class wxSocketServer
183 class wxSocketServer
: public wxSocketBase
187 Constructs a new server and tries to bind to the specified @e address.
189 Before trying to accept new connections, remember to test whether it succeeded
190 with wxSocketBase:IsOk().
193 Specifies the local address for the server (e.g. port number).
195 Socket flags (See wxSocketBase::SetFlags()).
197 wxSocketServer(const wxSockAddress
& address
,
198 wxSocketFlags flags
= wxSOCKET_NONE
);
201 Destructor (it doesn't close the accepted connections).
203 virtual ~wxSocketServer();
206 Accepts an incoming connection request, and creates a new wxSocketBase
207 object which represents the server-side of the connection.
209 If @a wait is @true and there are no pending connections to be
210 accepted, it will wait for the next incoming connection to
213 @warning This method will block the GUI.
215 If @a wait is @false, it will try to accept a pending connection
216 if there is one, but it will always return immediately without blocking
217 the GUI. If you want to use Accept() in this way, you can either check for
218 incoming connections with WaitForAccept() or catch @b wxSOCKET_CONNECTION events,
219 then call Accept() once you know that there is an incoming connection waiting
222 @return Returns an opened socket connection, or @NULL if an error
223 occurred or if the wait parameter was @false and there
224 were no pending connections.
226 @see WaitForAccept(), wxSocketBase::SetNotify(),
227 wxSocketBase::Notify(), AcceptWith()
229 wxSocketBase
* Accept(bool wait
= true);
232 Accept an incoming connection using the specified socket object.
235 Socket to be initialized
237 See Accept() for more info.
239 @return Returns @true on success, or @false if an error occurred or
240 if the wait parameter was @false and there were no pending
243 @see WaitForAccept(), wxSocketBase::SetNotify(),
244 wxSocketBase::Notify(), Accept()
246 bool AcceptWith(wxSocketBase
& socket
, bool wait
= true);
249 Wait for an incoming connection.
251 Use it if you want to call Accept() or AcceptWith() with @e wait set
252 to @false, to detect when an incoming connection is waiting to be accepted.
255 Number of seconds to wait. If -1, it will wait for the default
256 timeout, as set with wxSocketBase::SetTimeout().
258 Number of milliseconds to wait.
260 @return @true if an incoming connection arrived, @false if the timeout
263 @see Accept(), AcceptWith(), wxSocketBase::InterruptWait()
265 bool WaitForAccept(long seconds
= -1, long millisecond
= 0);
270 @class wxSocketClient
277 class wxSocketClient
: public wxSocketBase
284 Socket flags (See wxSocketBase::SetFlags())
286 wxSocketClient(wxSocketFlags flags
= wxSOCKET_NONE
);
289 Destructor. Please see wxSocketBase::Destroy().
291 virtual ~wxSocketClient();
294 Connects to a server using the specified address.
296 If @a wait is @true, Connect() will wait until the connection
299 @warning This method will block the GUI.
301 If @a wait is @false, Connect() will try to establish the connection
302 and return immediately, without blocking the GUI. When used this way,
303 even if Connect() returns @false, the connection request can be
304 completed later. To detect this, use WaitOnConnect(), or catch
305 @b wxSOCKET_CONNECTION events (for successful establishment) and
306 @b wxSOCKET_LOST events (for connection failure).
309 Address of the server.
311 If @true, waits for the connection to complete.
313 @return @true if the connection is established and no error occurs.
314 If @a wait was true, and Connect() returns @false, an error
315 occurred and the connection failed.
316 If @a wait was @false, and Connect() returns @false, you should
317 still be prepared to handle the completion of this connection request,
318 either with WaitOnConnect() or by watching wxSOCKET_CONNECTION
319 and wxSOCKET_LOST events.
321 @see WaitOnConnect(), wxSocketBase::SetNotify(), wxSocketBase::Notify()
323 virtual bool Connect(const wxSockAddress
& address
, bool wait
= true);
326 Connects to a server using the specified address.
328 If @a wait is @true, Connect() will wait until the connection
329 completes. @b Warning: This will block the GUI.
331 If @a wait is @false, Connect() will try to establish the connection
332 and return immediately, without blocking the GUI. When used this way,
333 even if Connect() returns @false, the connection request can be
334 completed later. To detect this, use WaitOnConnect(), or catch
335 @b wxSOCKET_CONNECTION events (for successful establishment) and
336 @b wxSOCKET_LOST events (for connection failure).
339 Address of the server.
341 Bind to the specified local address and port before connecting.
342 The local address and port can also be set using SetLocal(),
343 and then using the 2-parameter Connect() method.
345 If @true, waits for the connection to complete.
347 @return @true if the connection is established and no error occurs.
348 If @a wait was true, and Connect() returns @false, an error
349 occurred and the connection failed.
350 If @a wait was @false, and Connect() returns @false, you should
351 still be prepared to handle the completion of this connection request,
352 either with WaitOnConnect() or by watching wxSOCKET_CONNECTION
353 and wxSOCKET_LOST events.
355 @see WaitOnConnect(), wxSocketBase::SetNotify(), wxSocketBase::Notify()
357 bool Connect(const wxSockAddress
& address
, const wxSockAddress
& local
,
361 Wait until a connection request completes, or until the specified timeout
362 elapses. Use this function after issuing a call to Connect() with
363 @e wait set to @false.
366 Number of seconds to wait.
367 If -1, it will wait for the default timeout, as set with wxSocketBase::SetTimeout().
369 Number of milliseconds to wait.
372 WaitOnConnect() returns @true if the connection request completes.
373 This does not necessarily mean that the connection was
374 successfully established; it might also happen that the
375 connection was refused by the peer. Use wxSocketBase::IsConnected()
376 to distinguish between these two situations.
377 @n @n If the timeout elapses, WaitOnConnect() returns @false.
378 @n @n These semantics allow code like this:
380 // Issue the connection request
381 client->Connect(addr, false);
383 // Wait until the request completes or until we decide to give up
384 bool waitmore = true;
385 while ( !client->WaitOnConnect(seconds, millis) && waitmore )
387 // possibly give some feedback to the user,
388 // and update waitmore as needed.
390 bool success = client->IsConnected();
393 bool WaitOnConnect(long seconds
= -1, long milliseconds
= 0);
401 You are unlikely to need to use this class: only wxSocketBase uses it.
406 @see wxSocketBase, wxIPaddress, wxIPV4address
408 class wxSockAddress
: public wxObject
419 virtual ~wxSockAddress();
422 Delete all informations about the address.
424 virtual void Clear();
427 Returns the length of the socket address.
432 Returns the pointer to the low-level representation of the address.
434 This can be used to pass socket address information to a 3rd party
438 Pointer to a sockaddr-derived struct.
440 const sockaddr
*GetAddressData() const;
443 Returns the length of the buffer retrieved by GetAddressData().
446 The size of the sockaddr-derived struct corresponding to this
449 int GetAddressDataLen() const;
457 This event class contains information about socket events.
458 This kind of events are sent to the event handler specified with
459 wxSocketBase::SetEventHandler.
461 @beginEventTable{wxSocketEvent}
462 @event{EVT_SOCKET(id, func)}
463 Process a socket event, supplying the member function.
469 @see wxSocketBase, wxSocketClient, wxSocketServer
471 class wxSocketEvent
: public wxEvent
477 wxSocketEvent(int id
= 0);
480 Gets the client data of the socket which generated this event, as
481 set with wxSocketBase::SetClientData().
483 void* GetClientData() const;
486 Returns the socket object to which this event refers to.
487 This makes it possible to use the same event handler for different sockets.
489 wxSocketBase
* GetSocket() const;
492 Returns the socket event type.
494 wxSocketNotify
GetSocketEvent() const;
499 wxSocket error return values.
503 wxSOCKET_NOERROR
, ///< No error happened.
504 wxSOCKET_INVOP
, ///< Invalid operation.
505 wxSOCKET_IOERR
, ///< Input/Output error.
506 wxSOCKET_INVADDR
, ///< Invalid address passed to wxSocket.
507 wxSOCKET_INVSOCK
, ///< Invalid socket (uninitialized).
508 wxSOCKET_NOHOST
, ///< No corresponding host.
509 wxSOCKET_INVPORT
, ///< Invalid port.
510 wxSOCKET_WOULDBLOCK
, ///< The socket is non-blocking and the operation would block.
511 wxSOCKET_TIMEDOUT
, ///< The timeout for this operation expired.
512 wxSOCKET_MEMERR
///< Memory exhausted.
517 @anchor wxSocketEventFlags
519 wxSocket Event Flags.
521 A brief note on how to use these events:
523 The @b wxSOCKET_INPUT event will be issued whenever there is data available
524 for reading. This will be the case if the input queue was empty and new data
525 arrives, or if the application has read some data yet there is still more data
526 available. This means that the application does not need to read all available
527 data in response to a @b wxSOCKET_INPUT event, as more events will be produced
530 The @b wxSOCKET_OUTPUT event is issued when a socket is first connected with
531 Connect() or accepted with Accept(). After that, new events will be generated
532 only after an output operation fails with @b wxSOCKET_WOULDBLOCK and buffer space
533 becomes available again. This means that the application should assume that it can
534 write data to the socket until an @b wxSOCKET_WOULDBLOCK error occurs; after this,
535 whenever the socket becomes writable again the application will be notified with
536 another @b wxSOCKET_OUTPUT event.
538 The @b wxSOCKET_CONNECTION event is issued when a delayed connection request completes
539 successfully (client) or when a new connection arrives at the incoming queue (server).
541 The @b wxSOCKET_LOST event is issued when a close indication is received for the socket.
542 This means that the connection broke down or that it was closed by the peer. Also, this
543 event will be issued if a connection request fails.
545 enum wxSocketEventFlags
547 wxSOCKET_INPUT
, ///< There is data available for reading.
548 wxSOCKET_OUTPUT
, ///< The socket is ready to be written to.
549 wxSOCKET_CONNECTION
, ///< Incoming connection request (server), or
550 ///< successful connection establishment (client).
551 wxSOCKET_LOST
///< The connection has been closed.
556 @anchor wxSocketFlags
560 A brief overview on how to use these flags follows.
562 If no flag is specified (this is the same as @b wxSOCKET_NONE),
563 IO calls will return after some data has been read or written, even
564 when the transfer might not be complete. This is the same as issuing
565 exactly one blocking low-level call to @b recv() or @b send(). Note
566 that @e blocking here refers to when the function returns, not
567 to whether the GUI blocks during this time.
569 If @b wxSOCKET_NOWAIT is specified, IO calls will return immediately.
570 Read operations will retrieve only available data. Write operations will
571 write as much data as possible, depending on how much space is available
572 in the output buffer. This is the same as issuing exactly one nonblocking
573 low-level call to @b recv() or @b send(). Note that @e nonblocking here
574 refers to when the function returns, not to whether the GUI blocks during
575 this time. Also note that this flag impacts both Read and Write
576 operations. If it is desired to control Read independently of Write, for
577 example you want no wait on Read(), but you do want to wait on Write(), then
578 use wxSOCKET_NOWAIT_READ and wxSOCKET_NOWAIT_WRITE.
580 If @b wxSOCKET_NOWAIT_READ (this flag is new since wxWidgets 2.9.5) is
581 specified, Read operations will return immediately. Read operations will
582 retrieve only available data. This is the same as issuing exactly one
583 nonblocking low-level call to @b recv(). Note that @e nonblocking here
584 refers to when the function returns, not to whether the GUI blocks during
585 this time. This flag should not be enabled if ReadMsg() is going to be
586 used (it will be ignored), if you do then thread-safety may be at risk.
587 Note that wxSOCKET_NOWAIT_READ impacts only Read operations and does not
588 impact Write operations, allowing Read and Write operations to be set
591 If @b wxSOCKET_NOWAIT_WRITE (this flag is new since wxWidgets 2.9.5) is
592 specified, Write operations will return immediately. Write operations will
593 write as much data as possible, depending on how much space is available in
594 the output buffer. This is the same as issuing exactly one nonblocking
595 low-level call to @b send(). Note that @e nonblocking here refers to when
596 the function returns, not to whether the GUI blocks during this time. This
597 flag should not be enabled if WriteMsg() is going to be used (it will be
598 ignored), if you use it then thread safety may be at risk. Note that
599 wxSOCKET_NOWAIT_WRITE impacts only Write operations and does not impact
600 Write operations, allowing Read and Write operations to be set differently.
602 If @b wxSOCKET_WAITALL is specified, IO calls won't return until ALL
603 the data has been read or written (or until an error occurs), blocking if
604 necessary, and issuing several low level calls if necessary. This is the
605 same as having a loop which makes as many blocking low-level calls to
606 @b recv() or @b send() as needed so as to transfer all the data. Note
607 that @e blocking here refers to when the function returns, not
608 to whether the GUI blocks during this time. Note that wxSOCKET_WAITALL
609 impacts both Read and Write operations. If you desire to wait
610 for all on just Read operations, but not on Write operations, (or vice versa),
611 use wxSOCKET_WAITALL_READ or wxSOCKET_WAITALL_WRITE.
613 If @b wxSOCKET_WAITALL_READ (this flag is new since wxWidgets 2.9.5) is
614 specified, Read operations won't return until ALL the data has been read
615 (or until an error occurs), blocking if necessary, and issuing several low
616 level calls if necessary. This is the same as having a loop which makes as
617 many blocking low-level calls to @b recv() as needed so as to transfer all
618 the data. Note that @e blocking here refers to when the function returns,
619 not to whether the GUI blocks during this time. Note that
620 wxSOCKET_WAITALL_READ only has an impact on Read operations, and has no
621 impact on Write operations, allowing Read and Write operations to have
624 If @b wxSOCKET_WAITALL_WRITE (this flag is new since wxWidgets 2.9.5) is
625 specified, Write() and WriteMsg() calls won't return until ALL the data has
626 been written (or until an error occurs), blocking if necessary, and issuing
627 several low level calls if necessary. This is the same as having a loop
628 which makes as many blocking low-level calls to @b send() as needed so as
629 to transfer all the data. Note that @e blocking here refers to when the
630 function returns, not to whether the GUI blocks during this time. Note
631 that wxSOCKET_WAITALL_WRITE only has an impact on Write operations, and has
632 no impact on Read operations, allowing Read and Write operations to have
635 The @b wxSOCKET_BLOCK flag controls whether the GUI blocks during
636 IO operations. If this flag is specified, the socket will not yield
637 during IO calls, so the GUI will remain blocked until the operation
638 completes. If it is not used, then the application must take extra
639 care to avoid unwanted reentrance.
641 The @b wxSOCKET_REUSEADDR flag controls the use of the @b SO_REUSEADDR standard
642 @b setsockopt() flag. This flag allows the socket to bind to a port that is
643 already in use. This is mostly used on UNIX-based systems to allow rapid starting
644 and stopping of a server, otherwise you may have to wait several minutes for the
645 port to become available.
647 @b wxSOCKET_REUSEADDR can also be used with socket clients to (re)bind to a
648 particular local port for an outgoing connection.
649 This option can have surprising platform dependent behaviour, so check the
650 documentation for your platform's implementation of setsockopt().
652 Note that on BSD-based systems(e.g. Mac OS X), use of
653 @b wxSOCKET_REUSEADDR implies @b SO_REUSEPORT in addition to
654 @b SO_REUSEADDR to be consistent with Windows.
656 The @b wxSOCKET_BROADCAST flag controls the use of the @b SO_BROADCAST standard
657 @b setsockopt() flag. This flag allows the socket to use the broadcast address,
658 and is generally used in conjunction with @b wxSOCKET_NOBIND and
659 wxIPaddress::BroadcastAddress().
662 - @b wxSOCKET_NONE will try to read at least SOME data, no matter how much.
663 - @b wxSOCKET_NOWAIT will always return immediately, even if it cannot
664 read or write ANY data.
665 - @b wxSOCKET_WAITALL will only return when it has read or written ALL
667 - @b wxSOCKET_BLOCK has nothing to do with the previous flags and
668 it controls whether the GUI blocks.
669 - @b wxSOCKET_REUSEADDR controls special platform-specific behaviour for
670 reusing local addresses/ports.
674 wxSOCKET_NONE
= 0, ///< Normal functionality.
675 wxSOCKET_NOWAIT
= 1, ///< Read/write as much data as possible and return immediately.
676 wxSOCKET_WAITALL
= 2, ///< Wait for all required data to be read/written unless an error occurs.
677 wxSOCKET_BLOCK
= 4, ///< Block the GUI (do not yield) while reading/writing data.
678 wxSOCKET_REUSEADDR
= 8, ///< Allows the use of an in-use port.
679 wxSOCKET_BROADCAST
= 16, ///< Switches the socket to broadcast mode
680 wxSOCKET_NOBIND
= 32, ///< Stops the socket from being bound to a specific
681 ///< adapter (normally used in conjunction with
682 ///< @b wxSOCKET_BROADCAST)
683 wxSOCKET_NOWAIT_READ
= 64, ///< Read as much data as possible and return immediately
684 wxSOCKET_WAITALL_READ
= 128, ///< Wait for all required data to be read unless an error occurs.
685 wxSOCKET_NOWAIT_WRITE
= 256, ///< Write as much data as possible and return immediately
686 wxSOCKET_WAITALL_WRITE
= 512 ///< Wait for all required data to be written unless an error occurs.
693 wxSocketBase is the base class for all socket-related objects, and it
694 defines all basic IO functionality.
697 When using wxSocket from multiple threads, even implicitly (e.g. by using
698 wxFTP or wxHTTP in another thread) you must initialize the sockets from the
699 main thread by calling Initialize() before creating the other ones.
701 @beginEventEmissionTable{wxSocketEvent}
702 @event{EVT_SOCKET(id, func)}
703 Process a @c wxEVT_SOCKET event.
704 See @ref wxSocketEventFlags and @ref wxSocketFlags for more info.
710 @see wxSocketEvent, wxSocketClient, wxSocketServer, @sample{sockets},
711 @ref wxSocketFlags, ::wxSocketEventFlags, ::wxSocketError
713 class wxSocketBase
: public wxObject
718 @name Construction and Destruction
725 Don't use it directly; instead, use wxSocketClient to construct a socket client,
726 or wxSocketServer to construct a socket server.
733 Do not destroy a socket using the delete operator directly;
734 use Destroy() instead. Also, do not create socket objects in the stack.
736 virtual ~wxSocketBase();
739 Destroys the socket safely.
741 Use this function instead of the delete operator, since otherwise socket events
742 could reach the application even after the socket has been destroyed. To prevent
743 this problem, this function appends the wxSocket to a list of object to be deleted
744 on idle time, after all events have been processed. For the same reason, you should
745 avoid creating socket objects in the stack.
747 Destroy() calls Close() automatically.
749 @return Always @true.
754 Perform the initialization needed in order to use the sockets.
756 This function is called from wxSocket constructor implicitly and so
757 normally doesn't need to be called explicitly. There is however one
758 important exception: as this function must be called from the main
759 (UI) thread, if you use wxSocket from multiple threads you must call
760 Initialize() from the main thread before creating wxSocket objects in
763 It is safe to call this function multiple times (only the first call
764 does anything) but you must call Shutdown() exactly once for every call
767 This function should only be called from the main thread.
770 @true if the sockets can be used, @false if the initialization
771 failed and sockets are not available at all.
773 static bool Initialize();
776 Shut down the sockets.
778 This function undoes the call to Initialize() and must be called after
779 every successful call to Initialize().
781 This function should only be called from the main thread, just as
784 static void Shutdown();
795 Returns @true if an error occurred in the last IO operation.
797 Use this function to check for an error condition after one of the
798 following calls: Discard(), Peek(), Read(), ReadMsg(), Unread(), Write(), WriteMsg().
803 Return the local address of the socket.
805 @return @true if no error happened, @false otherwise.
807 virtual bool GetLocal(wxSockAddress
& addr
) const;
810 Return the peer address field of the socket.
812 @return @true if no error happened, @false otherwise.
814 virtual bool GetPeer(wxSockAddress
& addr
) const;
817 Return the socket timeout in seconds.
819 The timeout can be set using SetTimeout() and is 10 minutes by default.
821 long GetTimeout() const;
824 Returns @true if the socket is connected.
826 bool IsConnected() const;
829 Check if the socket can be currently read or written.
831 This might mean that queued data is available for reading or, for streamed
832 sockets, that the connection has been closed, so that a read operation will
833 complete immediately without blocking (unless the @b wxSOCKET_WAITALL flag
834 is set, in which case the operation might still block).
839 Returns @true if the socket is not connected.
841 bool IsDisconnected() const;
844 Returns @true if the socket is initialized and ready and @false in other
848 For wxSocketClient, IsOk() won't return @true unless the client is connected to a server.
849 For wxSocketServer, IsOk() will return @true if the server could bind to the specified address
850 and is already listening for new connections.
851 IsOk() does not check for IO errors; use Error() instead for that purpose.
856 Returns the number of bytes read or written by the last IO call.
858 Use this function to get the number of bytes actually transferred
859 after using one of the following IO calls: Discard(), Peek(), Read(),
860 ReadMsg(), Unread(), Write(), WriteMsg().
863 This function is kept mostly for backwards compatibility. Use
864 LastReadCount() or LastWriteCount() instead. LastCount() is still
865 needed for use with less commonly used functions: Discard(),
866 Peek(), and Unread().
868 wxUint32
LastCount() const;
871 Returns the number of bytes read by the last Read() or ReadMsg()
872 call (receive direction only).
874 This function is thread-safe, in case Read() is executed in a
875 different thread than Write(). Use LastReadCount() instead of
876 LastCount() for this reason.
878 Unlike LastCount(), the functions Discard(), Peek(), and Unread()
879 are currently not supported by LastReadCount().
883 wxUint32
LastReadCount() const;
886 Returns the number of bytes written by the last Write() or WriteMsg()
887 call (transmit direction only).
889 This function is thread-safe, in case Write() is executed in a
890 different thread than Read(). Use LastWriteCount() instead of
891 LastCount() for this reason.
895 wxUint32
LastWriteCount() const;
898 Returns the last wxSocket error. See @ref wxSocketError .
901 This function merely returns the last error code,
902 but it should not be used to determine if an error has occurred (this
903 is because successful operations do not change the LastError value).
904 Use Error() first, in order to determine if the last IO call failed.
905 If this returns @true, use LastError() to discover the cause of the error.
907 wxSocketError
LastError() const;
910 Restore the previous state of the socket, as saved with SaveState().
912 Calls to SaveState() and RestoreState() can be nested.
919 Save the current state of the socket in a stack.
921 Socket state includes flags, as set with SetFlags(), event mask, as set
922 with SetNotify() and Notify(), user data, as set with SetClientData().
923 Calls to SaveState and RestoreState can be nested.
935 See also: wxSocketServer::WaitForAccept(), wxSocketClient::WaitOnConnect()
940 Shut down the socket, disabling further transmission and reception of
941 data and disable events for the socket and frees the associated system
944 Upon socket destruction, Close() is automatically called, so in most cases
945 you won't need to do it yourself, unless you explicitly want to shut down
946 the socket, typically to notify the peer that you are closing the connection.
949 Although Close() immediately disables events for the socket, it is possible
950 that event messages may be waiting in the application's event queue.
951 The application must therefore be prepared to handle socket event messages even
952 after calling Close().
954 virtual bool Close();
957 Shuts down the writing end of the socket.
959 This function simply calls the standard shutdown() function on the
960 underlying socket, indicating that nothing will be written to this
963 void ShutdownOutput();
966 Delete all bytes in the incoming queue.
968 This function always returns immediately and its operation is not
969 affected by IO flags.
971 Use LastCount() to verify the number of bytes actually discarded.
973 If you use Error(), it will always return @false.
975 wxSocketBase
& Discard();
978 Returns current IO flags, as set with SetFlags()
980 wxSocketFlags
GetFlags() const;
983 Use this function to interrupt any wait operation currently in progress.
985 Note that this is not intended as a regular way to interrupt a Wait call,
986 but only as an escape mechanism for exceptional situations where it is
987 absolutely necessary to use it, for example to abort an operation due to
988 some exception or abnormal problem. InterruptWait is automatically called
989 when you Close() a socket (and thus also upon
990 socket destruction), so you don't need to use it in these cases.
992 @see Wait(), WaitForLost(), WaitForRead(), WaitForWrite(),
993 wxSocketServer::WaitForAccept(), wxSocketClient::WaitOnConnect()
995 void InterruptWait();
998 Peek into the socket by copying the next bytes which would be read by
999 Read() into the provided buffer.
1001 Peeking a buffer doesn't delete it from the socket input queue, i.e.
1002 calling Read() will return the same data.
1004 Use LastCount() to verify the number of bytes actually peeked.
1006 Use Error() to determine if the operation succeeded.
1009 Buffer where to put peeked data.
1013 @return Returns a reference to the current object.
1016 The exact behaviour of Peek() depends on the combination of flags being used.
1017 For a detailed explanation, see SetFlags()
1019 @see Error(), LastError(), LastCount(), SetFlags()
1021 wxSocketBase
& Peek(void* buffer
, wxUint32 nbytes
);
1024 Read up to the given number of bytes from the socket.
1026 Use LastReadCount() to verify the number of bytes actually read.
1027 Use Error() to determine if the operation succeeded.
1030 Buffer where to put read data.
1034 @return Returns a reference to the current object.
1037 The exact behaviour of Read() depends on the combination of flags being used.
1038 For a detailed explanation, see SetFlags()
1040 @see Error(), LastError(), LastReadCount(),
1043 wxSocketBase
& Read(void* buffer
, wxUint32 nbytes
);
1046 Receive a message sent by WriteMsg().
1048 If the buffer passed to the function isn't big enough, the remaining
1049 bytes will be discarded. This function always waits for the buffer to
1050 be entirely filled, unless an error occurs.
1052 Use LastReadCount() to verify the number of bytes actually read.
1054 Use Error() to determine if the operation succeeded.
1057 Buffer where to put read data.
1061 @return Returns a reference to the current object.
1064 ReadMsg() will behave as if the @b wxSOCKET_WAITALL flag was always set
1065 and it will always ignore the @b wxSOCKET_NOWAIT flag.
1066 The exact behaviour of ReadMsg() depends on the @b wxSOCKET_BLOCK flag.
1067 For a detailed explanation, see SetFlags().
1068 For thread safety, in case ReadMsg() and WriteMsg() are called in
1069 different threads, it is a good idea to call
1070 SetFlags(wxSOCKET_WAITALL|wx_SOCKET_BLOCK) before the first calls
1071 to ReadMsg() and WriteMsg() in different threads, as each of these
1072 functions will call SetFlags() which performs read/modify/write. By
1073 setting these flags before the multi-threading, it will ensure that
1074 they don't get reset by thread race conditions.
1076 @see Error(), LastError(), LastReadCount(), SetFlags(), WriteMsg()
1078 wxSocketBase
& ReadMsg(void* buffer
, wxUint32 nbytes
);
1081 Use SetFlags to customize IO operation for this socket.
1083 The @a flags parameter may be a combination of flags ORed together.
1084 Notice that not all combinations of flags affecting the IO calls
1085 (Read() and Write()) make sense, e.g. @b wxSOCKET_NOWAIT can't be
1086 combined with @b wxSOCKET_WAITALL nor with @b wxSOCKET_BLOCK.
1088 The following flags can be used:
1090 @flag{wxSOCKET_NONE}
1091 Default mode: the socket will read some data in the IO calls and
1092 will process events to avoid blocking UI while waiting for the data
1093 to become available.
1094 @flag{wxSOCKET_NOWAIT}
1095 Don't wait for the socket to become ready in IO calls, read as much
1096 data as is available -- potentially 0 bytes -- and return
1098 @flag{wxSOCKET_WAITALL}
1099 Don't return before the entire amount of data specified in IO calls
1100 is read or written unless an error occurs. If this flag is not
1101 specified, the IO calls return as soon as any amount of data, even
1102 less than the total number of bytes, is processed.
1103 @flag{wxSOCKET_BLOCK}
1104 Don't process the UI events while waiting for the socket to become
1105 ready. This means that UI will be unresponsive during socket IO.
1106 @flag{wxSOCKET_REUSEADDR}
1107 Allows the use of an in-use port (wxServerSocket only).
1108 @flag{wxSOCKET_BROADCAST}
1109 Switches the socket to broadcast mode.
1110 @flag{wxSOCKET_NOBIND}
1111 Stops the socket from being bound to a specific adapter (normally
1112 used in conjunction with @b wxSOCKET_BROADCAST).
1115 For more information on socket events see @ref wxSocketFlags .
1117 void SetFlags(wxSocketFlags flags
);
1120 Set the local address and port to use.
1122 This function must always be called for the server sockets but may also
1123 be called for client sockets, if it is, @b bind() is called before @b
1126 virtual bool SetLocal(const wxIPV4address
& local
);
1129 Set the default socket timeout in seconds.
1131 This timeout applies to all IO calls, and also to the Wait() family of
1132 functions if you don't specify a wait interval. Initially, the default
1133 timeout is 10 minutes.
1135 void SetTimeout(long seconds
);
1138 Put the specified data into the input queue.
1140 The data in the buffer will be returned by the next call to Read().
1142 This function is not affected by wxSocket flags.
1144 If you use LastCount(), it will always return @a nbytes.
1146 If you use Error(), it will always return @false.
1149 Buffer to be unread.
1153 @return Returns a reference to the current object.
1155 @see Error(), LastCount(), LastError()
1157 wxSocketBase
& Unread(const void* buffer
, wxUint32 nbytes
);
1160 Wait for any socket event.
1162 Possible socket events are:
1163 @li The socket becomes readable.
1164 @li The socket becomes writable.
1165 @li An ongoing connection request has completed (wxSocketClient only)
1166 @li An incoming connection request has arrived (wxSocketServer only)
1167 @li The connection has been closed.
1169 Note that it is recommended to use the individual @b WaitForXXX()
1170 functions to wait for the required condition, instead of this one.
1173 Number of seconds to wait.
1174 If -1, it will wait for the default timeout,
1175 as set with SetTimeout().
1177 Number of milliseconds to wait.
1180 @true when any of the above conditions is satisfied or @false if the
1181 timeout was reached.
1183 @see InterruptWait(), wxSocketServer::WaitForAccept(),
1184 WaitForLost(), WaitForRead(),
1185 WaitForWrite(), wxSocketClient::WaitOnConnect()
1187 bool Wait(long seconds
= -1, long millisecond
= 0);
1190 Wait until the connection is lost.
1192 This may happen if the peer gracefully closes the connection or if the
1196 Number of seconds to wait.
1197 If -1, it will wait for the default timeout,
1198 as set with SetTimeout().
1200 Number of milliseconds to wait.
1202 @return Returns @true if the connection was lost, @false if the timeout
1205 @see InterruptWait(), Wait()
1207 bool WaitForLost(long seconds
= -1, long millisecond
= 0);
1210 Wait until the socket is readable.
1212 This might mean that queued data is available for reading or, for streamed
1213 sockets, that the connection has been closed, so that a read operation will
1214 complete immediately without blocking (unless the @b wxSOCKET_WAITALL flag
1215 is set, in which case the operation might still block).
1217 Notice that this function should not be called if there is already data
1218 available for reading on the socket.
1221 Number of seconds to wait.
1222 If -1, it will wait for the default timeout,
1223 as set with SetTimeout().
1225 Number of milliseconds to wait.
1227 @return Returns @true if the socket becomes readable, @false on timeout.
1229 @see InterruptWait(), Wait()
1231 bool WaitForRead(long seconds
= -1, long millisecond
= 0);
1234 Wait until the socket becomes writable.
1236 This might mean that the socket is ready to send new data, or for streamed
1237 sockets, that the connection has been closed, so that a write operation is
1238 guaranteed to complete immediately (unless the @b wxSOCKET_WAITALL flag is set,
1239 in which case the operation might still block).
1241 Notice that this function should not be called if the socket is already
1245 Number of seconds to wait.
1246 If -1, it will wait for the default timeout,
1247 as set with SetTimeout().
1249 Number of milliseconds to wait.
1251 @return Returns @true if the socket becomes writable, @false on timeout.
1253 @see InterruptWait(), Wait()
1255 bool WaitForWrite(long seconds
= -1, long millisecond
= 0);
1258 Write up to the given number of bytes to the socket.
1260 Use LastWriteCount() to verify the number of bytes actually written.
1262 Use Error() to determine if the operation succeeded.
1265 Buffer with the data to be sent.
1269 @return Returns a reference to the current object.
1273 The exact behaviour of Write() depends on the combination of flags being used.
1274 For a detailed explanation, see SetFlags().
1276 @see Error(), LastError(), LastWriteCount(), SetFlags()
1278 wxSocketBase
& Write(const void* buffer
, wxUint32 nbytes
);
1281 Sends a buffer which can be read using ReadMsg().
1283 WriteMsg() sends a short header before the data so that ReadMsg()
1284 knows how much data should be actually read.
1286 This function always waits for the entire buffer to be sent, unless an
1289 Use LastWriteCount() to verify the number of bytes actually written.
1291 Use Error() to determine if the operation succeeded.
1294 Buffer with the data to be sent.
1296 Number of bytes to send.
1298 @return Returns a reference to the current object.
1302 WriteMsg() will behave as if the @b wxSOCKET_WAITALL flag was always set and
1303 it will always ignore the @b wxSOCKET_NOWAIT flag. The exact behaviour of
1304 WriteMsg() depends on the @b wxSOCKET_BLOCK flag. For a detailed explanation,
1306 For thread safety, in case ReadMsg() and WriteMsg() are called in
1307 different threads, it is a good idea to call
1308 @code SetFlags(wxSOCKET_WAITALL|wx_SOCKET_BLOCK) @endcode before the
1309 first calls to ReadMsg() and WriteMsg() in different threads, as each
1310 of these functions calls SetFlags() which performs read/modify/write.
1311 By setting these flags before the multi-threading, it will ensure that
1312 they don't get reset by thread race conditions.
1314 @see Error(), LastError(), LastWriteCount(), SetFlags(), ReadMsg()
1317 wxSocketBase
& WriteMsg(const void* buffer
, wxUint32 nbytes
);
1323 @name Handling Socket Events
1328 Returns a pointer of the client data for this socket, as set with
1331 void* GetClientData() const;
1334 According to the @a notify value, this function enables
1335 or disables socket events. If @a notify is @true, the events
1336 configured with SetNotify() will
1337 be sent to the application. If @a notify is @false; no events
1340 void Notify(bool notify
);
1343 Sets user-supplied client data for this socket. All socket events will
1344 contain a pointer to this data, which can be retrieved with
1345 the wxSocketEvent::GetClientData() function.
1347 void SetClientData(void* data
);
1350 Sets an event handler to be called when a socket event occurs. The
1351 handler will be called for those events for which notification is
1352 enabled with SetNotify() and
1356 Specifies the event handler you want to use.
1358 The id of socket event.
1360 @see SetNotify(), Notify(), wxSocketEvent, wxEvtHandler
1362 void SetEventHandler(wxEvtHandler
& handler
, int id
= -1);
1365 Specifies which socket events are to be sent to the event handler.
1366 The @a flags parameter may be combination of flags ORed together. The
1367 following flags can be used:
1370 @flag{wxSOCKET_INPUT_FLAG} to receive @b wxSOCKET_INPUT.
1371 @flag{wxSOCKET_OUTPUT_FLAG} to receive @b wxSOCKET_OUTPUT.
1372 @flag{wxSOCKET_CONNECTION_FLAG} to receive @b wxSOCKET_CONNECTION.
1373 @flag{wxSOCKET_LOST_FLAG} to receive @b wxSOCKET_LOST.
1379 sock.SetNotify(wxSOCKET_INPUT_FLAG | wxSOCKET_LOST_FLAG);
1383 In this example, the user will be notified about incoming socket data and
1384 whenever the connection is closed.
1386 For more information on socket events see @ref wxSocketEventFlags .
1388 void SetNotify(wxSocketEventFlags flags
);
1396 @class wxDatagramSocket
1403 class wxDatagramSocket
: public wxSocketBase
1412 Socket flags (See wxSocketBase::SetFlags()).
1414 wxDatagramSocket(const wxSockAddress
& addr
,
1415 wxSocketFlags flags
= wxSOCKET_NONE
);
1418 Destructor. Please see wxSocketBase::Destroy().
1420 virtual ~wxDatagramSocket();
1423 Write a buffer of @a nbytes bytes to the socket.
1425 Use wxSocketBase::LastWriteCount() to verify the number of bytes actually wrote.
1426 Use wxSocketBase::Error() to determine if the operation succeeded.
1429 The address of the destination peer for this data.
1431 Buffer where read data is.
1435 @return Returns a reference to the current object.
1437 @see wxSocketBase::LastError(), wxSocketBase::SetFlags()
1439 wxDatagramSocket
& SendTo(const wxSockAddress
& address
,
1440 const void* buffer
, wxUint32 nbytes
);