You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/05/04 03:52:16 UTC

[jira] [Updated] (TS-449) Split RecordsConfig.cc into "modules"

     [ https://issues.apache.org/jira/browse/TS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-449:
-----------------------------

    Fix Version/s:     (was: sometime)
    
> Split RecordsConfig.cc into "modules"
> -------------------------------------
>
>                 Key: TS-449
>                 URL: https://issues.apache.org/jira/browse/TS-449
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Leif Hedstrom
>            Priority: Minor
>
> To modularize configurations, we ought to split proxy/mgmt2/RecordsConfig.cc into each "module". This is/was partially done, albeit very incomplete, for "iocore". What I'd suggest we do is something like
> 1) Create a RecordsConfig.cc for each "module" that has configurations. This should allow for the same "capabilities" as the old RecordsConfig.cc, and should use the same APIs / format for all modules.
> 2) Once migrated over to a "module" specific RecordsConfig.cc, eliminate it from the old proxy/mgmt2/RecordsConfig.cc.
> This allows for "per-module" migration over to the new layout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira