/pidgin/main: e6c37a5e6666: New dependency: libcurl

Tomasz Wasilczyk tomkiewicz.groups at gmail.com
Wed Oct 10 16:29:52 EDT 2012


I have prepared proposal for our new HTTP API [1]. It currently
doesn't support easily handled POST fields - it can be added later,
without breaking API (just extending it).

It also doesn't support raw requests, because:
- most of not supported features can be easily emulated by handling of
parsed http headers
- if there would be any feature not possible to handle here, we can
just add such new feature to our API
- it would be hard (and buggy) to handle such raw requests (for
example: redirects)

After introducing it, our current HTTP code (purple_util_fetch_url*)
could be removed from API, marked deprecated and slowly removed from
libpurple code by replacing with purple_http_get and

Waiting for comments,

[1] http://pastebin.com/QnQHSDsL

2012/10/8 Tomasz Wasilczyk <tomkiewicz.groups at gmail.com>:
> I don't think, there is any library that fits better into our requirements.
> So, if using libcurl with its current limitations is undesirable, I have
> another proposal. We may create a new, extendable http api, with our
> implementation. When libcurl (or any other library) will gain required
> features, we will switch to it.
> Current API is horrible to use when making more complex requests (it
> requires manually built requests).
> Tomek

More information about the Devel mailing list