[jira] [Commented] (TS-3033) reimplement management protocol
[ https://issues.apache.org/jira/browse/TS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162309#comment-14162309 ] ASF subversion and git services commented on TS-3033: - Commit 355c165adc43eb838cc24652125b3c919a6f0e15 in trafficserver's branch refs/heads/master from [~jpe...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=355c165 ] TS-3033: fix PROXY_STATE_GET 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.3.4#6332)
[jira] [Commented] (TS-3033) reimplement management protocol
[ https://issues.apache.org/jira/browse/TS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14115335#comment-14115335 ] ASF subversion and git services commented on TS-3033: - Commit ab5f308661b519d74f0caceb2ec571536c604283 in trafficserver's branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ab5f308 ] TS-3033 Test for FD_SETSIZE, since Ubuntu detects the overflow 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)
[jira] [Commented] (TS-3033) reimplement management protocol
[ https://issues.apache.org/jira/browse/TS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112403#comment-14112403 ] ASF subversion and git services commented on TS-3033: - Commit 7c8284acbd35e7704029382fd4c6f03b231e2d19 in trafficserver's branch refs/heads/master from [~amc] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=7c8284a ] TS-3033: Fix build errors. 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)
[jira] [Commented] (TS-3033) reimplement management protocol
[ https://issues.apache.org/jira/browse/TS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110737#comment-14110737 ] ASF subversion and git services commented on TS-3033: - Commit e6f56c5cfbb1bb90e29f30b34845ee161a32a41b in trafficserver's branch refs/heads/master from [~amc] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=e6f56c5 ] TS-3033: Build error fixes. 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)
[jira] [Commented] (TS-3033) reimplement management protocol
[ https://issues.apache.org/jira/browse/TS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109917#comment-14109917 ] ASF subversion and git services commented on TS-3033: - Commit 3b5694136c2529516554dbdee3cfcb8944ba83f9 in trafficserver's branch refs/heads/master from [~jpe...@apache.org] [ 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)
[jira] [Commented] (TS-3033) reimplement management protocol
[ https://issues.apache.org/jira/browse/TS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109918#comment-14109918 ] ASF subversion and git services commented on TS-3033: - Commit 6250f431bb6c0d61b55aa21bd7a00b7d059a73a9 in trafficserver's branch refs/heads/master from [~jpe...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=6250f43 ] TS-3033: reimplement management API with generic marshalling This reimplements the management protocol on top of the generic message marshalling API. 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)
