[
https://issues.apache.org/jira/browse/TS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109917#comment-14109917
]
ASF subversion and git services commented on TS-3033:
-----------------------------------------------------
Commit 3b5694136c2529516554dbdee3cfcb8944ba83f9 in trafficserver's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=3b56941 ]
TS-3033: generic message initial marshalling
Implement a very simple generic message marshalling API. This is
similar to the existing hand-rolled marshalling, except that there
are fewer data types, and it is all implemented in a single place.
Add MgmtSocket.cc because there's really no benefit to having all
the mgmt socket wrappers inline. Move some more helper API over to
MgmtSocket.
> reimplement management protocol
> -------------------------------
>
> Key: TS-3033
> URL: https://issues.apache.org/jira/browse/TS-3033
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, Management API
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 5.2.0
>
>
> The management protocol is hand-crafted for each message type. That's a lot
> of code and it makes it unnecessarily complicated to add new message types.
> Let's introduce a simple, generic marshaling format and use that everywhere.
> The format I have implemented can be used for signaling traffic_server as
> well, but for now this is just changing API messages to traffic_manager.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
