comparison ChangeLog.API @ 30153:35a1cf247168

Add network listen functions that accept a family argument (AF_INET(6?)). These allow code to portably support IPv6 for listeners (mostly file transfers and Bonjour). Callers should use the purple_socket_speaks_ipv4 to determine whether they need two sockets or just an IPv6 one. I used GIO's g_socket_speaks_ipv4 as the inspiration for that.
author Paul Aurich <paul@darkrain42.org>
date Sat, 17 Apr 2010 01:27:04 +0000
parents 4d0ccbc905aa
children 933c8251e036
comparison
equal deleted inserted replaced
30152:5be4137c4a68 30153:35a1cf247168
17 * purple_media_manager_set_backend_type 17 * purple_media_manager_set_backend_type
18 * purple_network_get_all_local_system_ips, which returns all local 18 * purple_network_get_all_local_system_ips, which returns all local
19 IPs on the system. On systems with the getifaddrs() function, 19 IPs on the system. On systems with the getifaddrs() function,
20 this will return both IPv4 and IPv6 addresses (excluding link-local 20 this will return both IPv4 and IPv6 addresses (excluding link-local
21 and loopback addresses). On others, it returns just IPv4 addresses. 21 and loopback addresses). On others, it returns just IPv4 addresses.
22 * purple_network_listen_family and
23 purple_network_listen_range_family. These will replace the
24 versions without _family in 3.0.0 and allow the caller to
25 specifically request either an IPv4 or IPv6 socket. IPv6 is
26 only supported if the getaddrinfo() function is available
27 at build-time (not the case on Windows, currently).
22 * purple_prpl_got_media_caps 28 * purple_prpl_got_media_caps
29 * purple_socket_get_family
30 * purple_socket_speaks_ipv4
23 * purple_unescape_text 31 * purple_unescape_text
24 * purple_uuid_random 32 * purple_uuid_random
25 * media_caps to the PurpleBuddy struct 33 * media_caps to the PurpleBuddy struct
26 * buddy-caps-changed blist signal 34 * buddy-caps-changed blist signal
27 * ui-caps-changed media manager signal 35 * ui-caps-changed media manager signal