> -Original Message-
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Sent: Monday, November 02, 2009 5:18 PM
> To: Tomcat Users List
> Subject: RE: Compression and SSL
>
> Thanks for all the suggestions so far guys.
> Are there any other tip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 11/3/2009 3:06 AM, André Warnier wrote:
> You have to look at
> it from the browser's point of view. When it sees an "incomplete" link,
> it completes it using the protocol and hostname from which the current
> page was obtained, and then i
at Users List
Subject: Re: Compression and SSL
Can I get more granular? I'd be happy for a pointer to a good reference
on the subject.
There are probably tons on Google, if you look for "website
optimi[z,s]ation" or the like.
Personally, I have found that a very large proportion
, i.e. we have to customize some files that would be in the
WAR.
Jeff
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: Tuesday, November 03, 2009 4:41 AM
To: Tomcat Users List
Subject: Re: Compression and SSL
Peter Crowther wrote:
...
> Jeffrey's since confirm
--Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: Tuesday, November 03, 2009 2:07 AM
To: Tomcat Users List
Subject: Re: Compression and SSL
> Can I get more granular? I'd be happy for a pointer to a good reference
> on the subject.
There are probably tons on Go
On 03/11/2009 10:40, André Warnier wrote:
Peter Crowther wrote:
...
Jeffrey's since confirmed it's not a CPU issue - thanks Jeffrey! - so I
agree that bandwidth/latency is the one to solve, as the rest of the
thread's been working on while I've been asleep!
Elaborating a bit on what I mentione
Peter Crowther wrote:
...
Jeffrey's since confirmed it's not a CPU issue - thanks Jeffrey! - so I
agree that bandwidth/latency is the one to solve, as the rest of the
thread's been working on while I've been asleep!
Elaborating a bit on what I mentioned before, and sorry Jeffrey if this
sounds
2009/11/2 George Sexton
> You didn't read the original post very closely.
>
> >> to serve applications from the US to Asia-based clients.
>
> It's bandwidth and latency.
>
Actually, yes, I did. And I saw that, and I suspected latency would be the
answer. Suspicion is not confirmation however :
ll probably pay off big time.
Even a cheap low power server might offer a better service if the
resources are small enough, and it's in the locality.
p
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Monday, November 02, 2009 12:12 PM
To: Tomcat Users List
Subj
Jeffrey Janner wrote:
Thanks for all the suggestions so far guys.
Are there any other tips I could provide to the developers that they can
do to improve throughput?
Should they hard-code the http:// for all the static elements to avoid
passing them over SSL,
If these items are not sensitive, t
com]
Sent: Monday, November 02, 2009 1:56 PM
To: 'Tomcat Users List'
Subject: RE: Compression and SSL
> -Original Message-
> From: peter.crowth...@googlemail.com
> [mailto:peter.crowth...@googlemail.com] On Behalf Of Peter Crowther
> Sent: Monday, November 02, 2009
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Will setting the HTTPS connector "compression=on" actually compress the
>> data for HTTPS?
>Any reason to suspect it wouldn't?
Some result from a Google search I did trying to find a solution to this issue
led me to infer that
ter Crowther
Sent: Monday, November 02, 2009 1:35 PM
To: Tomcat Users List
Subject: Re: Compression and SSL
2009/11/2 George Sexton
> In general, Compressing HTML can help a great deal for any case
besides a
> local network.
>
... or a CPU-limited server.
To the OP: What's the bottle
PM
To: Tomcat Users List
Subject: Re: Compression and SSL
Jeffrey Janner wrote:
> OK, another newbie-ish question here.
>
Then a dummy-ish answer may be sufficient :
>
> Will setting the HTTPS connector "compression=on" actually compress the
> data for HTTPS?
It w
r.com]
Sent: Monday, November 02, 2009 12:12 PM
To: Tomcat Users List
Subject: Re: Compression and SSL
On 02/11/2009 16:48, Jeffrey Janner wrote:
> OK, another newbie-ish question here.
>
>
>
> I am using Tomcat 5.5.x with APR/native libraries on Windows 2003 x32
or
> Wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 11/2/2009 11:48 AM, Jeffrey Janner wrote:
> We encrypt everything using SSL, from Login page onward, with
> of CONFIDENTIAL.
[snip]
> Response time is noticeably slow (based on complaint level) and I am
> looking for ways to improve it
> -Original Message-
> From: peter.crowth...@googlemail.com
> [mailto:peter.crowth...@googlemail.com] On Behalf Of Peter Crowther
> Sent: Monday, November 02, 2009 12:35 PM
> To: Tomcat Users List
> Subject: Re: Compression and SSL
>
> 2009/11/2 George S
2009/11/2 George Sexton
> In general, Compressing HTML can help a great deal for any case besides a
> local network.
>
... or a CPU-limited server.
To the OP: What's the bottleneck in your environment? CPU? Disk I/O?
Network bandwidth? Measure the problem, *then* look for solutions to the
pr
> -Original Message-
> From: Pid [mailto:p...@pidster.com]
> Sent: Monday, November 02, 2009 11:12 AM
> To: Tomcat Users List
> Subject: Re: Compression and SSL
>
> On 02/11/2009 16:48, Jeffrey Janner wrote:
> > OK, another newbie-ish question here.
> >
&g
Jeffrey Janner wrote:
OK, another newbie-ish question here.
Then a dummy-ish answer may be sufficient :
Will setting the HTTPS connector "compression=on" actually compress the
data for HTTPS?
It will compress all data it would compress it it wasn't HTTPS.
Does it compress before or afte
On 02/11/2009 16:48, Jeffrey Janner wrote:
OK, another newbie-ish question here.
I am using Tomcat 5.5.x with APR/native libraries on Windows 2003 x32 or
Windows 2008 x64 to serve applications from the US to Asia-based
clients.
We encrypt everything using SSL, from Login page onward, with
o
21 matches
Mail list logo
