[wildfly-dev] HTTP/2 out of the box in Wildfly 10.1
Jason Greene
jason.greene at redhat.com
Fri Jun 3 14:06:44 EDT 2016
> On Jun 3, 2016, at 9:28 AM, Jorge Solórzano <jorsol at gmail.com> wrote:
>
> IMO this feature should be oriented to sysadmins not just developers. Is there really added value for developers to use HTTPS or HTTPS/2?
Yeah, server push is an example, we have an API where you can push resources to the client before they are requested. Although we have a learning handler that can try to do it for you, but thats not as good as something designed for it. It also has different characteristics that you can exploit (e.g. being able to create a lot of streams without impacting connection count) that you might want to do if you are building an HTTP/2 centric application. Of course, not everyone will fall into this category because they will need to support both h2 and h1.
>
> It should be easy for sysadmins to setup TLS/SSL with "production" quality, from the gereration of the CSR that has to be send to the CA to the generation of the keystone.
Agreed. What Stuart meant was that out of the box auto-generation was a development focused feature. Obviously in production you don’t need /want keys automatically generated, you want to use your publicly signed cert.
>
> BTW... how is the performance of HTTPS using pure Java vs Apache for example? is this feature oriented for developers because for use in production is not recommended?
Java based SSL is certainly usable and performant in production, many people deploy on it.
>
>
> Ing. Jorge Solórzano
> about.me/jorsol <https://about.me/jorsol?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links>
>
> On Fri, Jun 3, 2016 at 3:52 AM, Tomaž Cerar <tomaz.cerar at gmail.com <mailto:tomaz.cerar at gmail.com>> wrote:
> This is completely off topic for this thread, there was one earlier about what should go into 10.x....
>
> Anywho, issue you mention was already resolved and hibernate updated in master some time ago.
> which means it will be in next release, whatever that release will be.
>
> --
> tomaz
>
> On Thu, Jun 2, 2016 at 6:29 PM, Harold Campbell <hcamp at muerte.net <mailto:hcamp at muerte.net>> wrote:
> On Thu, 2016-06-02 at 09:22 +1000, Stuart Douglas wrote:
> > Hi All,
> >
> > I would like to propose that we add support for HTTP/2 out of the box
> > in Wildfly 10.1.
> >
>
> This lowly user desperately wants a release containing the fix to WFLY-
> 6283 sooner rather than later. I'm sure other people have other pet
> bugs awaiting release.
>
> I have no opinion on HTTP/2 being added other than to ask that pent up
> bug fixes be kept in mind.
>
> --
> Harold Campbell <hcamp at muerte.net <mailto:hcamp at muerte.net>>
>
> Roses are red;
> Violets are blue.
> I'm schizophrenic,
> And so am I.
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160603/207706c8/attachment-0001.html
More information about the wildfly-dev
mailing list