summaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Use GProxyResolver for all proxy resolvingDan Winship2013-07-134-24/+19
| | | | | | | | | | | | | Finish up the GProxyResolver porting started in 2.42 by removing all the non-GProxyResolver proxy code from SoupSocket and SoupConnection and implementing SoupSession:proxy-uri in terms of GSimpleProxyResolver. If the user adds a SoupProxyResolverDefault to the session, just use its GProxyResolver directly instead. If the user adds any other kind of SoupProxyURIResolver to the session, use the new SoupProxyResolverWrapper, which is a GProxyResolver that translates from SoupProxyURIResolver. https://bugzilla.gnome.org/show_bug.cgi?id=680273
* Rename SoupKnownStatusCode to SoupStatusDan Winship2013-07-131-1/+2
| | | | | | | | | | Rename SoupKnownStatusCode to SoupStatus (so that the type name matches the enum values), and then, for backward-compatibility, add a new SoupKnownStatusCode enum with equivalent values so that introspection-using code that was doing "SoupKnownStatusCode.OK", etc, will still work. https://bugzilla.gnome.org/show_bug.cgi?id=684409
* use libfffi-based generic marshaller instead of glib-genmarshalOlivier Blin2013-06-081-1/+1
| | | | | | | g_cclosure_marshal_generic() is the default signal handler starting from glib 2.29.12. libsoup already requires glib 2.33.1. https://bugzilla.gnome.org/show_bug.cgi?id=686042
* soup-message-queue: add a priority system to the message queueSergio Villar Senin2013-04-171-0/+5
| | | | | | | | Clients can specify a priority for each message added to the SoupSession, which will determine the order in which it is processed by the session's message processing queue. https://bugzilla.gnome.org/show_bug.cgi?id=696277
* Added version 2.44 definesSergio Villar Senin2013-04-171-0/+4
|
* soup-session: add SoupMessage-based streaming APIsDan Winship2013-01-141-0/+4
| | | | | | SoupRequestHTTP is now implemented in terms of SoupSession SoupMessage operations, so we might as well just expose those directly, for people who want streaming APIs, but not SoupRequest.
* Rename LIBSOUP_DISABLE_DEPRECATED to SOUP_DISABLE_DEPRECATEDDan Winship2013-01-041-1/+1
| | | | | | | | | GNOME_MAINTAINER_MODE_DEFINES apparently sets LIBSOUP_DISABLE_DEPRECATED, which is now causing various jhbuild modules to break. "Fix" this by renaming the define (which is only still there because gtk-doc complains if it's not). The *right* way to get deprecation warnings/errors now is to define SOUP_VERSION_MIN_REQUIRED.
* soup-auth-manager: add soup_auth_manager_use_auth()Dan Winship2013-01-022-0/+46
| | | | | | Add soup_auth_manager_use_auth(), for "preloading" authentication, and make the old automatically-request-NTLM behavior happen only for the legacy SoupSession subclasses.
* SoupAuthManager: make this publicDan Winship2013-01-023-1/+18
|
* soup-auth-manager: split out connection handlingDan Winship2013-01-022-1/+2
| | | | | | | | | | | | Add a new SoupConnectionAuth class to help with connection tracking, and make SoupAuthNTLM a subclass of it. Allow a single SoupAuthNTLM to carry state information about multiple connections. Make SoupSession store the SoupConnection a SoupMessage is associated with on the message, and use that from SoupConnectionAuth rather than tracking sockets by hand like SoupAuthManager had previously done. Remove the connection tracking in SoupAuthManager, since it is no longer needed.
* SoupSession: update docs (and some semantics) for plain SoupSessionDan Winship2012-12-284-1/+169
| | | | | | | Update the docs to reflect the changes in plain SoupSessions vs its traditional subclasses. And while we're there, add a few new ones (including making soup_session_queue_message() and soup_session_send_message() work on plain SoupSession.
* Revert the mirroring of SoupMessage API onto SoupRequestHTTP.Dan Winship2012-12-281-10/+0
| | | | | | | | | | | SoupMessage isn't being deprecated, and mirroring its API onto SoupRequestHTTP is just going to result in always having to add every new API twice. Also, it turns out to be less useful than originally expected anyway, since you end up having to cast between SoupRequest and SoupRequestHTTP frequently anyway. This reverts commit d7117329400e47d2187ed033099d921d555f8d71 and most of commit 53c270d0e2868fa5ad48ce864f10a9486b11a071.
* Add back LIBSOUP_DISABLE_DEPRECATEDDan Winship2012-12-281-1/+1
| | | | | | gtk-doc expects "Deprecated:" notes in docs to be matched up with some deprecation-guard #define. So even though we don't want people to use it any more, add LIBSOUP_DISABLE_DEPRECATED back.
* docs: more fixesDan Winship2012-12-283-38/+38
|
* docs: Lots of minor fixes and additionsDan Winship2012-12-273-23/+52
|
* docs: remove libsoup-gnome references from the buildDan Winship2012-12-121-2/+1
| | | | | | | Since everything in libsoup-gnome is now deprecated and undocumented, don't depend on it when building docs. https://bugzilla.gnome.org/show_bug.cgi?id=573685
* soup-gnome: belatedly deprecate SoupProxyResolverGNOMEDan Winship2012-12-112-17/+0
| | | | | | | There's no real reason to use SoupProxyResolverGNOME rather than SoupProxyResolverDefault, so deprecate that too. libsoup-gnome now consists entirely of deprecated functions.
* Add SoupCookieJarDB to replace SoupCookieJarSqliteDan Winship2012-12-112-15/+14
| | | | | | | Move SoupCookieJarSqlite (and its sqlite3 dependency) into libsoup from libsoup-gnome, but rename it to SoupCookieJarDB so libsoup-gnome can keep using the old name. SoupCookieJarSqlite is now just a wrapper around SoupCookieJarDB.
* SoupSession: add soup_session_request_http() and _request_http_uri()Dan Winship2012-12-101-0/+2
| | | | | Add SoupSession helpers to return SoupRequestHTTP directly and allow overriding the request method.
* SoupRequest: add soup_request_disable_feature()Dan Winship2012-12-101-0/+2
| | | | | | | | | Add soup_request_disable_feature(), which proxies to soup_message_disable_feature() for SoupRequestHTTP and is a no-op otherwise. Add SoupRequest tests to sniffing-test, which also tests soup_request_disable_feature() now.
* SoupMessage: add soup_message_get_soup_request()Dan Winship2012-12-101-0/+1
| | | | | | When dealing with SoupMessage-related signals in SoupRequest-using code, it's useful to be able to get the message's associated SoupRequest.
* SoupRequestHTTP: mirror SoupMessage fields/APIDan Winship2012-12-101-0/+8
| | | | | Mirror various SoupMessage-related API onto SoupRequestHTTP so that you don't need to resort to soup_request_http_get_message().
* Move SoupRequester API into SoupSession, declare SoupRequest stableDan Winship2012-12-102-35/+15
| | | | | | | | | | | | Add soup_session_request() and soup_session_request_uri(), implementing basically the same behavior as soup_requester_request() and soup_requester_request_uri() (but without requiring a separate SoupSessionFeature), and remove the unstable-api ifdefs from soup-request*.h. SoupRequester still exists, but it is still guarded by the unstable-api ifdefs, and is just a dummy wrapper around the functionality that is now in SoupSession.
* build: distcheck fixes, including one generic srcdir!=builddir fixDan Winship2012-11-101-4/+7
|
* Add per-version deprecation/availability warningsDan Winship2012-11-081-1/+13
| | | | | | | | | | | Add SOUP_VERSION_X_XX, SOUP_VERSION_MIN_REQUIRED, and SOUP_VERSION_MAX_ALLOWED, to enable version-based warnings. Tag all functions with appropriate SOUP_AVAILABLE_IN_ and SOUP_DEPRECATED_IN_ macros. Also, fix up some "Since" tags to not refer to unstable releases or non-.0 point releases.
* Add API to get version informationMartin Robinson2012-10-222-0/+16
| | | | | | | | Expose API to get information about the soup version. This is useful because it allows applications to use API without actually depending on it completely. https://bugzilla.gnome.org/show_bug.cgi?id=684514
* soup-request: Add support to handle gresource URI requestsCarlos Garcia Campos2012-10-201-0/+1
| | | | | | | | | GFile already supports gresource when using g_file_new_for_uri() with a resource:// URI. We can add "resource" as a valid scheme for SoupRequestFile and make sure the GFile is created with the gresource URI for gresource requests. https://bugzilla.gnome.org/show_bug.cgi?id=682721
* Add SoupMultipartInputStream for handling multipart responsesGustavo Noronha Silva2012-08-202-0/+16
| | | | | | | | SoupMultipartInputStream can be used by the API user to wrap the input stream, and provides API to obtain the next part and its headers, using a SoupFilterInputStream internally for buffer management. https://bugzilla.gnome.org/show_bug.cgi?id=656684
* soup-tld: added soup_tld_* utilsSergio Villar Senin2012-06-142-1/+14
| | | | | | | | | The soup_tld_* set of functions along with the list of public suffixes published in http://publicsuffix.org allows API clients to get the base domain of a given hostname or to check if a given domain is a public suffix (one under which internet users can register new names). https://bugzilla.gnome.org/show_bug.cgi?id=673802
* Bug 677923 - Add soup_cookie_jar_set_cookie_with_first_party() alternative ↵Christophe Dumez2012-06-121-0/+1
| | | | | | | | | | | | | that takes a SoupCookie in argument Currently, the only way to add a cookie while checking first_party is to use soup_cookie_jar_set_cookie_with_first_party(). However, this function takes an unparsed cookie in argument. In the event the client has already parsed the cookie (e.g. to do some pre-processing), it would be useful to have an alternative to soup_cookie_jar_set_cookie_with_first_party() which takes a parsed SoupCookie in argument. This would be more efficient.
* Bug 677922 - Add soup_cookie_jar_get_cookies() alternative that returns a ↵Christophe Dumez2012-06-121-0/+1
| | | | | | | | GSList of SoupCookies Adds a soup_cookie_jar_get_cookie_list() function that returns the cookies in the jar that would be sent with a request to a specific uri, as a GSList of SoupCookies.
* soup-message-body: Add a soup_buffer_get_as_bytes methodJasper St. Pierre2012-05-241-0/+1
| | | | | | | This new method will return a GBytes instance containing the contents of the SoupBuffer. https://bugzilla.gnome.org/show_bug.cgi?id=676776
* soup-cookie-jar: Add SoupCookieJar:is-persistent propertyCarlos Garcia Campos2012-04-181-0/+2
| | | | | | | It allows to query whether cookies are stored persisently by the SoupCookieJar. https://bugzilla.gnome.org/show_bug.cgi?id=672838
* gtk-doc fixesDan Winship2012-03-262-5/+9
|
* soup-session.c: add soup_session_prefetch_dnsSergio Villar Senin2012-03-181-0/+1
| | | | | | | | | This deprecates soup_session_prepare_for_uri(). It basically does the same, i.e., it lets the session prepare for a possible upcoming request by doing DNS resolution. It additionally has cancellation support and adds a callback to notify the caller when the operation finishes. https://bugs.webkit.org/show_bug.cgi?id=41630
* Require glib 2.31 and update to new thread APIsDan Winship2011-12-011-1/+1
|
* SoupSession: add some API for handling redirectionsDan Winship2011-11-051-0/+4
|
* SoupSession: Add http-aliases and https-aliases propertiesDan Winship2011-11-051-0/+2
| | | | | | | | | | | | | Currently SoupSession treats all URI schemes except "https" as aliases for "http", and some apps depend on this. (Eg, iTunes sometimes returns redirects involving "daap" URIs, which Rhythmbox needs to treat as "http".) Unfortunately, this also means that it mishandles redirects to, eg, ftp. The http-aliases and https-aliases properties allow an app to explicitly indicate which URI schemes should be considered aliases for http and https, with other schemes considered to be unknown and unhandled.
* Lots of gtk-doc fixes (no code changes)Dan Winship2011-09-226-914/+312
|
* docs: fix typo in client-howtoDan Winship2011-05-211-1/+1
| | | | | Patch from Davide Italiano https://bugzilla.gnome.org/show_bug.cgi?id=650526
* Fix docs build for pickier linkersDan Winship2011-05-031-1/+4
| | | | | Patch from "arno" https://bugzilla.gnome.org/show_bug.cgi?id=648948
* SoupProxyResolverGNOME: make this a subclass of SoupProxyResolverDefaultDan Winship2011-03-211-2/+1
| | | | | | | | | | | | | | | modify SoupProxyResolverDefault so it's possible to override the choice of g_proxy_resolver_get_default(), and make SoupProxyResolverGNOME just be a subclass of SoupProxyResolverDefault that specifically requests the "gnome" GProxyResolver. libsoup-gnome no longer depends on libproxy and GConf. (Perhaps it should now depend on gsettings-desktop-schemas, or else a glib-networking that includes GProxyResolverGnome. But it will fall back to using the libproxy-based proxy resolver in that case anyway, so it's all good.) https://bugzilla.gnome.org/show_bug.cgi?id=625898
* Add gobject-introspection supportAndreas Rottmann2010-04-261-0/+4
| | | | | | | | | | | | | | | - Detect gobject-introspection (g-i) in configure, using the M4 macro from the newly-added introspection.m4. This adds gobject-introspection as a new *optional* build dependency. - Integrate the generation of .gir and .typelib files into the build build process. - Add the annotations from gir-repository to the source code. - Include annotation glossary in "Reference Manual" main file. See <https://bugzilla.gnome.org/show_bug.cgi?id=576595>.
* Misc gtk-doc updatesDan Winship2010-02-213-21/+4
|
* Fix header names in build-howto.xmlDan Winship2009-08-251-4/+4
| | | | Pointed out by Dominik Bylica
* Fix up docsDan Winship2009-08-103-21/+48
|
* another out-of-tree build fixDan Winship2009-08-091-1/+1
|
* Build fixesAndreas Rottmann2009-08-091-0/+1
| | | | | - Add -I$(top_builddir) to documentation scanner CFLAGS (fixes "make distcheck" run from an out-of-tree build)
* Bug 576760 – soup_message_headers_get_content_type returns bad headersDan Winship2009-04-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | * libsoup/soup-message-headers.c (soup_message_headers_get_one) (soup_message_headers_get_list): New replacements for soup_message_headers_get(), indicating explicitly whether the caller expects the header to be a list or not; for non-list-type headers, if there's more than one, the second one should be ignored rather than concatenated to the first. (soup_message_headers_get): deprecate this. * libsoup/*.c: * tests/*.c: Update to use soup_message_headers_get_one() or _get_list() as appropriate. * tests/header-parsing.c (do_content_type_tests): Add some tests of Content-Type parsing/setting, including making sure that duplicate Content-Type headers are ignored. * docs/reference/libsoup-2.4-sections.txt: update svn path=/trunk/; revision=1258
* clarify that SoupSessionAsync is not thread-safe, and that setting aDan Winship2009-03-271-1/+12
| | | | | | | | | * docs/reference/client-howto.xml: clarify that SoupSessionAsync is not thread-safe, and that setting a non-default GMainContext on a non-threadsafe object means you can only use that object from that GMainContext's thread. svn path=/trunk/; revision=1255
View Lorry Controller Status