You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/07/28 11:27:01 UTC
[jira] [Updated] (INLONG-310) Upgrade WebAPI protocol: HTTP/1.1 =>
HTTP/2
[ https://issues.apache.org/jira/browse/INLONG-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated INLONG-310:
----------------------------------
Labels: pull-request-available (was: )
> Upgrade WebAPI protocol: HTTP/1.1 => HTTP/2
> -------------------------------------------
>
> Key: INLONG-310
> URL: https://issues.apache.org/jira/browse/INLONG-310
> Project: Apache InLong
> Issue Type: Sub-task
> Components: inlong-tubemq
> Reporter: Jeff Zhou
> Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> THIS IS AN OPTIONAL TASK.
> HTTP/2 could bring more intelligent control on Frames-based data submission (no longer a big form-data or alike), Interactive data exchange (Multiplexing/ServerPush mechanism), API QoS (Stream Prioritization), while current HTTP/1.1 could fulfill basic requirement of WebAPI.
> So it brings bigger possibility to WebAPI, but it may not be bright spot improvement for now (or maybe some day :)
> It's nice to discuss about it, and just implement it if this upgrade itself is straight-forward based on Jetty 9.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)