Hi Chris, I do not want to start a war but I am using Wildfly 9.0.0 CR1. The
initial reason I looked it was due to Undertow. Then I found out they had a
HTTP/2 implementation and when I tried that for half of my requests headers
went from 3xx bytes down to 3x bytes. The response times were a millisecond but
I expected that and they have put into place a measurement down to nanoseconds
since internally I am seeing less than microsecond sometimes from my cache
system. I plan to move away from Wildfly and use just Undertow if I can to have
a lighter container but it was advised to start with Wildfly to use Undertow.
For me I feel servlets are getting old and need to be replaced by something
else. Way to many layers to get to your application code. I also believe with
all the advancements in CPU and memory size that limiting to a single thread
when using stateless requests is a waste of capability. Incremental increases
in capability is a safe way to go but fun to try something leading edge even if
I have to create it myself.
Sorry about the rambling. I am still trying to get the servlet 4 implementation
release date. Best Regards to Apache,-Tony
From: Christopher Schultz <ch...@christopherschultz.net>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Friday, May 15, 2015 2:49 PM
Subject: Re: Http 2 support in Tomcat
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Tony,
On 5/15/15 2:43 PM, PerfGuru wrote:
> Thanks Mark & Chris this is a very informative. I am using a httpd
> that supports http/2 and wow is it impressive. Sorry, I had to
> stop using Apache/Tomcat to use it but the performance and
> bandwidth gains are so nice it is addicting and my users have
> noticed.
How does it compare to, say, HTTP/1.1 + Content-Encoding: gzip? I
realize that HTTP/1.1 never compresses the message headers and that
H/2 uses tokens and Huffman Coding to further compress the headers,
but I'd like to see some real-world data if you have it.
What server are you using?
> I will look into jre/jdk 9 and ask Oracle if servlet 4 is in the
> EA's. I would like to stay with http/2 rather than go to
> websockets but I am an early adopter and if it is stable and has
> servlet 4 with http/2 I will give it a try and let you know the
> results.
When Tomcat 9 goes Stable, HTTP/2 will definitely work. I'm sure there
will be some edge cases that will need to be fixed as time goes on,
but the spec will require H/2 and Tomcat will implement faithfully. We
don't want to merely say "oh, yeah, H/2 kinda works and, well, we HAD
to do it, so YMMV". We want to say "you can rely on Tomcat to serve
H/2 as well as H/1".
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJVVlvjAAoJEBzwKT+lPKRY3bwP/1wqb41Eu1fqN80MbrcUUdrJ
qnrWD4o9EsvpPo5Abe0mkGXwiP+F2blDKFRYSXolpuADbmMpsd2gLPjrEGiy6H/J
M6HFbjWPTAt4cIzscSZjAAUrpe05v0M39ZuV7z+nHXjT5UTyZQgmiNn3uvHPbVwQ
DnfwTReswgyi0E5O5Q3qRz32lP49OpZyLgvAEl4N2cd64a+7ScX1eMHpq/NuVuQ8
N+E/GdgsC+UFOO6DYKHNsn8/kOZ1B7oP4e9fmudnBDCXOFTfqB5lsgGRTkvdXQR8
6dJEq8PkkTxPt0tqdd0UAT6FcLU0Axsm/CzNtej5pj5mIUrt9e5PpRPLH8uk1h2/
waq88NyOxJoYKycngubgK/rL1IET7kJ/Nu4f4j4hFDhMxox1w3K9HrMdKogpPYCY
Uh7mdCphpjQxZirkwDnDlwOtbq+t66mNM/DJkeumQ3zfC3fe2wLevnDd7cNOEEx/
fj/r2GbB5p+EtOm67ysAyMc5STdobbueZO/ggBleD2tIiMxOcWE+sXbaXHNzydw4
y9phbm75Q2P8w8EslITnyqyTtbUdyAYJUAhy6nosHXujwwAp+wK+J1yfSzlu4a2w
fLjgp92QsYP5fcA7yyNv0zI0tIREKJwONyL+vd2DD1IGibdxKGssjCtUr0QkhpfT
BXvYpY5JXNoF0YDIEchy
=QGzZ
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
