view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

Revision history for Apache::Dynagzip

0.16  Sat Oct 09 19:30:00 2004
	- bugfix. Content-Type was overwritten to default text/html during the streaming of a static
	  file because $r->header_out('Content-Type') was not set, however $r->content_type is set
	  properly in PerlLibTreeTrans URI_Translation_Handler. Fixed in two places.
	- documentation was lightly edited, especially regarding the details of module installation
	  and appropriate mod_perl configuration. Thanks to Kevin Austin for the hints.
	- README was reformatted back to plain text.
	- META.yml was created manually and added to MANIFEST.

0.15  Sun May 02 15:11:00 2004
	- clean up: Dan Kubb has found some inconsistences in implementation of UseCGIHeadersFromScript
	  within the Filter chain. Documentation and the code were cleaned up in order to make sure

Dynagzip.pm  view on Meta::CPAN

That was why I came up with an idea to use chunked data transmission of
the gzipped content, sharing a real time between the server side data
creation/compression, media data transmission, and the client side data
decompression/presentation in order to provide end users with the partially
displayed content as soon as it's possible in particular conditions of the
user's connection.

At the time we decided to go for dynamic compression there were no
appropriate software on the market. Even later in
February 2002 Nicholas Oxhøj wrote to the mod_perl mailing list about his
experience of finding Apache gzipper for the streaming outgoing content:

=for html
<blockquote>

I<"... I have been experimenting with all the different Apache compression modules
I have been able to find, but have not been able to get the desired result.
I have tried Apache::GzipChain, Apache::Compress, mod_gzip and mod_deflate, with
different results.  One I cannot get to work at all. Most work, but seem to collect
all the output before compressing it and sending it to the browser...>

I<... Wouldn't it be nice to have some option to specify that the handler should flush
and send the currently compressed output every time it had received a certain amount
of input or every time it had generated a certain amount of output?..>

I<... So I am basically looking for anyone who has had any success in achieving this
kind of "streaming" compression, who could direct me at an appropriate Apache module.">

=for html
</blockquote>

Unfortunately for him, C<Apache::Dynagzip> has not yet been publicly available at that time...

Since relesed this handler is especially useful when one needs to compress the outgoing
web content that is dynamically generated on the fly using templates,
DB data, XML, etc., and when at the time of the request it is impossible
to determine the length of the response.