You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tubemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/08/06 14:00:00 UTC

[jira] [Commented] (TUBEMQ-308) Upgrade Jetty 6 (mortbay) => Jetty 9 (eclipse)

    [ https://issues.apache.org/jira/browse/TUBEMQ-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172390#comment-17172390 ] 

ASF subversion and git services commented on TUBEMQ-308:
--------------------------------------------------------

Commit bc4f280e75c7e97747dac979b39c9b8edd7a45b4 in incubator-tubemq's branch refs/heads/master from Gabriel Zhou
[ https://gitbox.apache.org/repos/asf?p=incubator-tubemq.git;h=bc4f280 ]

[TUBEMQ-308] Upgrade Jetty 6 (mortbay) => Jetty 9 (eclipse) (#232)

Co-authored-by: Gabriel Zhou <ga...@tencent.com>

> Upgrade Jetty 6 (mortbay) => Jetty 9 (eclipse)
> ----------------------------------------------
>
>                 Key: TUBEMQ-308
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-308
>             Project: Apache TubeMQ
>          Issue Type: Sub-task
>          Components: Server
>            Reporter: Jeff Zhou
>            Assignee: Jeff Zhou
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> This sub-task is for component upgrade.
> Currently using Jetty 6 is so old, which has stopped maintenance for 10+ years, and stay in HTTP 1.1, and the mechanism currently using based on Filters to start processing could be so hard to do feature extension and supporting POST request.
> So this could be the first step polishing TubeMQ WebAPI, to make it stay in latest.
> Attention: no WebAPI feature would be changed after this sub-task, it's a fundamental upgrade.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)