Re: 3.0.20 ChangeLog progress

Ian Silvester <[email protected]> wrote:

> So I've attached the 3.0.20 ChangeLog here for comment. I don't want to merge it into ChangeLog until it's had at least first-pass approval, plus I've listed here below a number of commit messages (and the file(s) they relate to) that I haven't yet included in the log, grouped under relevant headings; please suggest whether each should be added or not.

As far as I'm concerned the ChangeLog draft can be merged
and the few remaining issues fixed once it's in CVS.

Overall it looks good to me and I mainly intend to relocate a
couple of items and sort the items by significance. A few items
don't affect 3.0.20 as they address regressions introduced after
3.0.19 and can thus be deleted.

> Put this in the ChangeLog or just in the announcement?
> 
> 
>   - Enable tolerate-pipelining for the beta as discussed on ijbswa@

The fact that it is enabled should be mentioned in the
ChangeLog entry that describes the feature.

> Are all of these covered by other items I've already added to the ChangeLog? 
> 
> 
>   - Set the SERVER_CONTENT_LENGTH_SET flag after creating a new Content-Length header
> 
> This allows to keep the client connection alive after
> filtering a chunk-encoded response.
> 
> parsers.c, 
> 
> 
>   - Allow serve() to keep client connections open if the response content length is zero
> 
> jcc.c, 
> 
> 
>   - Keep track of how many requests have been received on a client socket
> 
> jcc.c, project.h, 
> 
> 
>   - Keep track of how many request are sent through a server connection
> 
> gateway.c, jcc.c, project.h, 
> 
> 
>   - Figure out the request length before running sed()
> 
> We may want to adjust the Connection header based on the information.
> 
> jcc.c, 
> 
> 
>   - Add get_expected_content_length()
> 
> parsers.c, parsers.h, 
> 
> 
>   - Let get_content_length() use a header value as input instead of the whole header
> 
> This makes it easier to use it in combination with get_header_value().
> 
> parsers.c, 

I think they can be merged to a single entry about being better at
reusing open connections.

> Can't find reference to this keyword in the documentation, and don't know how to represent it in the ChangeLog. Presume it's a new feature?
> 
> 
>   - Mention the shiny new LOG_LEVEL_ACTIONS
> 
> doc/source/p-config.sgml, 
> 
> 
>   - Add LOG_LEVEL_ACTIONS to log the applying actions
> 
> Unlike in the "Final results", the effect of tags is taken into account.

This is "debug 65536".
 
> Presume these are internal to the project and don't need entries in ChangeLog?

Correct. They only affect the website and are unrelated to the release.

Fabian

------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812

_______________________________________________
Ijbswa-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ijbswa-developers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlDv6SEACgkQSMVSH78upWNDJwCfX54z9PCBldqmr6KVY1st/Oxw
DVIAoIiyQw7ao4vYVFDqwkngwpEiHUv9
=MZ54
-----END PGP SIGNATURE-----