Author: jmb Date: Thu Oct 8 17:31:42 2009 New Revision: 9616 URL: http://source.netsurf-browser.org?rev=9616&view=rev Log: A couple more changes. I'm not sure I like this API. Modified: branches/jmb/new-cache/content/hlcache.h Modified: branches/jmb/new-cache/content/hlcache.h URL: http://source.netsurf-browser.org/branches/jmb/new-cache/content/hlcache.... ============================================================================== --- branches/jmb/new-cache/content/hlcache.h (original) +++ branches/jmb/new-cache/content/hlcache.h Thu Oct 8 17:31:42 2009 @@ -62,17 +62,19 @@ * \param flags Object retrieval flags * \param referer Referring URL, or NULL if none * \param post POST data, or NULL for a GET request + * \param width Available width for content + * \param height Available height for content * \param cb Callback to handle object events * \param pw Pointer to client-specific data for callback * \param parent Parent cache handle, or NULL if none * \param result Pointer to location to recieve cache handle * \return NSERROR_OK on success, appropriate error otherwise * - * \todo fetchcache() has width and height parameters. - * Do we really need to preserve those? + * \todo Is there any way to sensibly reduce the number of parameters here? */ nserror hlcache_handle_retrieve(const char *url, uint32_t flags, const char *referer, llcache_post_data *post, + uint32_t width, uint32_t height, hlcache_object_callback cb, void *pw, hlcache_handle *parent, hlcache_handle **result); @@ -92,7 +94,7 @@ * thing being that the client need not care about this possibility and can * just call the functions with impugnity. */ -nserror hlcache_handle_to_content(const hlcache_handle *handle, +nserror hlcache_handle_get_content(const hlcache_handle *handle, struct content **result); #endif