Am 29.06.16 um 17:43 schrieb Martin Grigorov:
On Tue, Jun 28, 2016 at 11:02 PM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:
Hi,
I just saw this old topic and want to give some information about HTTP/2
and Wicket.
First of all Wicket will have support for http
Hi Martin,
Am 29.06.16 um 17:43 schrieb Martin Grigorov:
On Tue, Jun 28, 2016 at 11:02 PM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:
Hi,
I just saw this old topic and want to give some information about HTTP/2
and Wicket.
First of all Wicket will have support for
aw this old topic and want to give some information about HTTP/2
>> and Wicket.
>>
>> First of all Wicket will have support for http/2 via PushBuilder API - A
>> PoC can be found here:
>>
>> https://github.com/klopfdreh/jetty-http2-example
>>
>> So bef
On Tue, Jun 28, 2016 at 11:02 PM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:
> Hi,
>
> I just saw this old topic and want to give some information about HTTP/2
> and Wicket.
>
> First of all Wicket will have support for http/2 via PushBuilder API - A
Hi,
I just saw this old topic and want to give some information about HTTP/2 and
Wicket.
First of all Wicket will have support for http/2 via PushBuilder API - A PoC
can be found here:
https://github.com/klopfdreh/jetty-http2-example
So before the actual page request is finished you can push
).
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Apr 2, 2016 at 9:37 AM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:
> Hi,
>
> I am trying to get http/2 working on Mac OS X 10.11.4 - these are the
> steps I used:
>
&g
Hi,
I am trying to get http/2 working on Mac OS X 10.11.4 - these are the steps
I used:
1. Install Brew: http://brew.sh/
2. Download Apache Tomcat 9 https://tomcat.apache.org/download-90.cgi
3. Download Xcode command line tools by opening the terminal and execute
“xcode-select —install”
4
but I have
> verified that both Google Chrome and Firefox report that the site is HTTP/2
> enabled.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Wed, Mar 2, 2016 at 5:16 PM, Lars Törner wrote:
>
> > Hi Martin,
> >
That's correct!
Honestly I haven't checked the network traffic to verify that all or at
least several resources are served in the same connection but I have
verified that both Google Chrome and Firefox report that the site is HTTP/2
enabled.
Martin Grigorov
Wicket Training and Consul
Hi Martin,
that sounds interesting!
So what you´re saying is that if the server where the wicket-applictation
is deployed supports http/2 then wicket itself doesn't need any
wicket-specific-extension to work. And that, for example, all components
css/javascript-resources of a page wi
Hi Lasse,
I have successfully tested a Wicket application (my WebSockets demo app) on
Tomcat 9.0.0.M1/M2/M3 (
https://twitter.com/mtgrigorov/status/665916977957982208) with HTTP/2.
Currently there is a discussion at Tomcat dev@ mailing list about porting
back the changes to Tomcat 8.5.0. 8.5 will
Hi,
I have some (naive?) questions:
- Isn't it time to think about wicket and http/2?
- Must we wait for javaee8/servlet 4.0 and then wait for a new version of
wicket that supports it?
- Is it possible to implement an extension to support http/2 in wicket?
- Is it a huge effort to make
12 matches
Mail list logo