From: SourceForge.net <no...@so...> - 2004-11-25 15:52:59
|
Patches item #1072290, was opened at 2004-11-24 01:01 Message generated for change (Comment added) made by faceprint You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300235&aid=1072290&group_id=235 Category: newfeature Group: None Status: Open Resolution: None Priority: 5 Submitted By: Manuel Amador (Rudd-O) (rudd-o) Assigned to: Nathan Walp (faceprint) Summary: HTTP POST + SSL + XMLRPC + Cookies Initial Comment: Here is a patch that does several things: a) create a new function called gaim_url_post, which allows developers to perform a (max 16K) HTTP POST against an HTTP server b) extend the gaim_url_post function with SSL capabilities, so https:// URIs can be used as well c) implement a simple, asynchronous XML-RPC interface, with (hopefully, as it seems from the Gaim source code) support for HTTP Basic authentication d) store cookies in an extremely simple settings cookie jar, for those Web servers These things can be very useful to e.g. plugin developers or core Gaim developers. Some things which now use an ad-hoc Web interface, like the release notification plugin, could very well be reimplemented using an XML-RPC interface. Apply with a lot of fuzz ---------------------------------------------------------------------- >Comment By: Nathan Walp (faceprint) Date: 2004-11-25 10:52 Message: Logged In: YES user_id=17471 16k is an arbitrary limit, and arbitrary limits are bad. you don't submit a patch and say "apply with a lot of fuzz", you submit a patch that applies. if you can't keep your patch in sync, what makes you think we want to? also, I don't feel the need to "fix" the release notification plugin that isn't broken, and I don't see any other use for this patch...we're not going to inflate the size of gaim to add an unused API. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300235&aid=1072290&group_id=235 |