RE: Representing HTTP Requests Responses and Headers in moki

> > Proposed answer: use the value= representation because then the
> > representation of unstructured values of headers, elements and
> > parameters is the same, it's the most compact way of doing it and it
> > adds to readability.
> 
> Sounds good -- would just ask that we "take this resolution" and you
> implement it in the code soon to stabilize the representation sooner
> rather than later to avoid backtracking and reimplementing tests
> later.
> 
OK I just committed some changes that make that happen.

Aside from any outstanding bugs, the remaining major task, HTTP
Header-wise is to put HTTP redirection support in, hopefully late this
afternoon. Oh, and to add support for DNS errors etc. Oh and probably
other stuff too ...

Jo

Received on Friday, 25 May 2007 10:36:34 UTC