Poly 1.2.0

Hi there,

	Polygraph 1.2.0 is available The change log is attached.
	http://polygraph.ircache.net/sources/

The major addition for this release is the Object Life Cycle model that
allows us to simulate object modification times, produce meaningful
Expires: header fields, handle If-Modified-Since requests, etc. In spite of
the relatively large number of command line options, the model is actually
quite easy to grasp and use. Details and examples are at
	http://polygraph.ircache.net/doc/objlife.html

Please read the change log carefully as some of the defaults have changed.

Enjoy,

Alex.

----------- change log --------------
1.1p0 -> 1.2.0
19990501
  - added Object Life Cycle model to simulate object modification and
    expiration; the model is controlled by the following server side
    options: --obj_life_cycle, --obj_life_cycle_var, --obj_with_lmt,
    and --obj_expire
  - support If-Modified-Since requests on server side
  - Poly-server now adds the Date: header field to all replies
  - removed "max-age" option from cachable replies because it had
    priority over the more common Expires: header. As a side effect
    not all cachable replies have expiration information
  - Last-Modified header field is now added to replies only if
    --obj_life_cycle option is enabled; some proxies will not cache
    replies without a Last-Modified header field -- watch out!
  - Expires header fields are not added to cachable replies by default;
    see --obj_expire option to control Expires fields
  - reordered HTTP reply header fields to follow HTTP recommendations
  - always use the minimum of FD_SETSIZE and getrlimit(RLIMIT_NOFILE);
    warn if FD_SETSIZE is smaller; we got tired of coredumps when
    a tester would forget to increase FD_SETSIZE after increasing
    kernel limits
  - date manipulation functions now use "timegm()" call which may
    not be portable; portability problems will be fixed on-demand
  - distinguish between "premature end of msg body" and "premature end
    of msg headers"; useful to diagnose proxy connection resets
  - detect premature end of headers on client side (we probably would
    wait forever prior to this fix)
  - reorganized and optimized HTTP header parsing; parsing speed is
    increasingly important as we have to recognize more header fields;
    current improvement (on 2.5 fields) is negligible (about 3%).
  - fixed a bug with HTTP header parsing (a patch was available for
    1.1.0)