On Fri, 19 Oct 2001, Sterling Hughes wrote:

> > How do we signal/offer the headers of the particular document we're getting?
> > I figure we shouldn't just return a block of data, we should somehow also
> > return a handle that could be used by the application to query on
> > specific details on the data (like if it is a header etc).
>
> hrmm, perhaps for the advanced functions we can skip this parsing?
> \r\n\r\n isn't really that hard to look for in a c application.

Isn't it? What if the first three bytes come in one buffer and the last one
in another?

Or... what if we made libcurl handle a protocol in which there is headers,
but they're not separated from the body the same way? \r\n\r\n is a very
HTTP/MIME-ish way...

> > We should write down the functions, document their expected behavior and we
> > could try writing some faked implementation of clients using it. Then it'll
> > be easier to implement the API. IMHO.

> I agree.

Will you take the first step?

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/