When I find some time I am going to file in a ticket. kind regards
Tobias > Am 29.06.2016 um 17:43 schrieb Martin Grigorov <mgrigo...@apache.org>: > > 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 >> PoC can be found here: >> >> https://github.com/klopfdreh/jetty-http2-example >> >> So before the actual page request is finished you can push several >> resources to the client via header item. >> >> The item itself is also compatible with http<2 because resources aren't >> pushed to the client at all in this case. >> >> There are some hints in the implementation that the client is going to >> have the option to activate / deactivate the push functionality. >> >> If a client has cached the resource already a RST_STREAM is send to the >> server to skip the next pushed resource so that there is no high traffic at >> all. >> >> @stackoverflow I asked a question regarding the client side caching in >> Jetty and a core dev already answered: >> >> >> http://stackoverflow.com/questions/37211883/jetty-respond-with-status-200-instead-of-304-while-using-http2 >> >> I am waiting for further hints at this point. > > There is no answer since May 20th. > I'd file an issue at Jetty bug tracker. > > >> >> If the JEE server supports HTTP/2 I think you are going to be able to ship >> files within the WEB-INF with push, too (this is only an assumption) >> >> Hope the dev regarding the JEE standard is continued soon. >> >> kind regards >> >> Tobias >> >>> Am 02.03.2016 um 19:43 schrieb Lars Törner <lars.tor...@gmail.com>: >>> >>> Ok, thanks! >>> >>> I hope to find the time to test it in the near future. :-) >>> >>> >>> 2016-03-02 17:30 GMT+01:00 Martin Grigorov <mgrigo...@apache.org>: >>> >>>> 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 Consulting >>>> https://twitter.com/mtgrigorov >>>> >>>>> On Wed, Mar 2, 2016 at 5:16 PM, Lars Törner <lars.tor...@gmail.com> >> wrote: >>>>> >>>>> 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 will be fetched over one multiplexed >>>>> connection. >>>>> >>>>> Cheers >>>>> Lasse >>>>> >>>>> >>>>> >>>>> 2016-03-02 16:40 GMT+01:00 Martin Grigorov <mgrigo...@apache.org>: >>>>> >>>>>> 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 be what 9.0 is now without >>>> the >>>>>> Servlet 4.x APIs because Servlet 4.x release date is far in the >> future. >>>>>> >>>>>> I have also was able to run Wicket app with Jetty SPDY impl in the >>>> past. >>>>>> >>>>>> I haven't tested with WildFly 10 but I don't expect any problems from >>>>>> Wicket side. >>>>>> Please let us know if you face any issues and we will investigate >> them! >>>>>> >>>>>> Thanks! >>>>>> >>>>>> >>>>>> Martin Grigorov >>>>>> Wicket Training and Consulting >>>>>> https://twitter.com/mtgrigorov >>>>>> >>>>>>> On Wed, Mar 2, 2016 at 4:31 PM, Lars Törner <lars.tor...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> 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 this happen? >>>>>>> >>>>>>> I think (most of?) the latest versions of the major browsers support >>>>>>> http/2, Wildfly supports http/2 server side with undertow... etc. >>>>>>> Known implementations of HTTP/2: >>>>>>> https://github.com/http2/http2-spec/wiki/Implementations >>>>>>> >>>>>>> I have read Martin G:s comment from a year back about this (see >>>> below), >>>>>> but >>>>>>> not found anything else... maybe there already is an ongoing >>>> discussion >>>>>>> about this? >>>>>>> >>>>>>> Cheers >>>>>>> Lasse >>>>>>> >>>>>>> ////Martins reflections about http/2 and servlet 4.0//// >>>>>>> I'm afraid it is too early for this. We can make sure Wicket works >>>> fine >>>>>> in >>>>>>> a container supporting those but it is too early to require that. >>>>> Servlet >>>>>>> 4.0 is still in design process. Apache Tomcat didn't started >>>>> implementing >>>>>>> any features from it. I am not sure about the status in Jetty. I know >>>>>> that >>>>>>> Undertow (the web container for JBoss Wildfly) supports HTTP 2.0 but >>>> I >>>>>>> haven't heard of any Servlet 4.0 features. It will take us some time >>>> to >>>>>>> release 8.0.0 but I think it will be too >>>>>>> early to require Servlet 4.0 even then. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
