Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Imaskar
    @Imaskar
    Hi. I've come across this interesting server recently. It looks great, but I see the latest commit was long ago. Is it still being developed? Any plans on http/2, for example?
    Mikhail Bobrutskov
    @wizzardo
    Hello, yes it's still in development, and I will focus more on it in a near future, cause I'm going to migrate my company's project from spring-boot to this framework
    I don't have any plans for http/2,
    Because I'm a bit disappointed in it, but maybe I will add it at some point
    Plan for near future: add compatibility-lib for spring-boot
    And rename the framework
    Mikhail Bobrutskov
    @wizzardo
    If you have any specific feature-request you can ask here or in GitHub-issues
    Btw, why do you need http2?
    Imaskar
    @Imaskar
    I don't specifically need it, I'm just exploring fast low memory profile web servers for java. Http/2 saves bandwidth, saves time on connecting, should be more resource-efficient. Why are you disappointed in it?
    Mikhail Bobrutskov
    @wizzardo
    because it doesn't have 2-way data flow like in websockets
    it has only one connection, that in real-world usually slower
    all the browsers allow http/2 only with encryption
    server-push is kinda useless because it ignores client-cache
    Mikhail Bobrutskov
    @wizzardo
    on my current project I'm using websockets to make a lot of requests to backend in parallel, something like 150 requests on app-start, and page loads in 900ms
    Imaskar
    @Imaskar
    Well, in theory, http/2 should provide at least more useful bandwidth than http/1.1. It will still be less that websockets, which doesn't send any headers at all. But it's not because of one connection. Have you measured http/1.1 vs http2?
    Imaskar
    @Imaskar
    You my be right that in modern scenarios restful frameworks don't need all this http stuff at all. Just pass json/protobuf over websocket and that will do.
    Imaskar
    @Imaskar
    But you will have to manually map each response to request... may not be worth it. And some clients do not support WS (I don't really know which ones). Socket.IO exists for some reason.
    Mikhail Bobrutskov
    @wizzardo
    Well, in theory, http/2 should provide at least more useful bandwidth than http/1.1. It will still be less that websockets, which doesn't send any headers at all. But it's not because of one connection. Have you measured http/1.1 vs http2?
    @Imaskar no I didn't compared them in any benchmark
    do you know any good benchmark?
    Imaskar
    @Imaskar
    I did a quick look and didn't find anything credible. The best I got is this https://imagekit.io/demo/http2-vs-http1 Most posts try to measure some [thought to be] real-world scenario. To measure maximum throughput I think its better to write one from scratch. It will be dependent on client performance, unfortunately.