tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Gamache <cgama...@gmail.com>
Subject Re: sendFiles vs. compression
Date Tue, 18 Apr 2017 17:41:46 GMT
On Tue, Apr 18, 2017 at 11:29 AM, Mark Thomas <markt@apache.org> wrote:

> On 18/04/17 15:58, Chris Gamache wrote:
> > Excellent information. Thank you!
> >
> > Is there a way to create a split point where sendFile will handle files
> of
> > certain mime types (or all mime-types except for an exclusion list of
> mime
> > types) and/or of certain sizes while compression will handle files of
> other
> > mime-types and/or certain sizes?
>
> No.
>
> > Both settings have a minimum file size that engages their mechanism but
> to
> > set up a division of labor I would think we would need all of
> > include/exclude and max/min for both sendfile() and compression. Again, I
> > could be missing something obvious by staring at the problem too long.
> >
> > @André and the rest of the listserv, In your opinions-- thinking about
> the
> > web site consumer's experience, and having to choose either send
> sendfile()
> > or compression-- is the juice worth the squeeze so-to-speak keeping
> > sendfile() and sending uncompressed files, or is the better choice to
> > enable compression at the expense of direct static file access and save
> > bandwidth?
>
> It will depend on your site and the typical traffic mix. You'd have to
> test it.
>
> Or...
>
> You can have the best of both worlds if you pre-compress your static
> resources. You need to be using 8.5.x or later. Look for precompressed
> on http://tomcat.apache.org/tomcat-8.5-doc/default-servlet.html
>
>
That's wicked. Something to look forward to when we are at the point of
jumping to 8.5 or beyond.


> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message