Date: Fri, 30 Dec 2005 15:20:27 -0500 From: Martin Cracauer <cracauer@cons.org> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: Martin Cracauer <cracauer@cons.org>, freebsd-current@freebsd.org, Colin Percival <cperciva@freebsd.org> Subject: Re: fetch extension - use local filename from content-dispositionheader (new diff) Message-ID: <20051230152027.A39043@cons.org> In-Reply-To: <86psne2wd2.fsf@xps.des.no>; from des@des.no on Fri, Dec 30, 2005 at 08:55:21PM %2B0100 References: <20051229221459.A17102@cons.org> <030d01c60cf1$db80a290$1200a8c0@gsicomp.on.ca> <20051230035724.GA52167@nagual.pp.ru> <20051230125227.A33408@cons.org> <43B580D2.9070609@freebsd.org> <20051230142848.A36879@cons.org> <86psne2wd2.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote on Fri, Dec 30, 2005 at 08:55:21PM +0100: > Martin Cracauer <cracauer@cons.org> writes: > > DES, can you be more specific in what way I break the API? > > You changed the size of struct url_stat. Not to argue but that is an ABI change, not an API one. I certainly don't see how this qualifies as "disgusting" as you put it. Ok, how about I change the inline struct to a constructor/pointer-passing mechanism (with changed names) and we bump the shared library version number? That way fields can be added in an ABI and API backwards-compatible manner in the future. The way it is organized right now libfetch effectivly shields the application from HTTP headers and the API chosen for header information transportation is locked against extensions. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051230152027.A39043>