You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Zhao Yongming (Created) (JIRA)" <ji...@apache.org> on 2011/10/24 11:39:32 UTC
[jira] [Created] (TS-1003) prefetch: the config file
prefetch: the config file
-------------------------
Key: TS-1003
URL: https://issues.apache.org/jira/browse/TS-1003
Project: Traffic Server
Issue Type: Sub-task
Reporter: Zhao Yongming
Assignee: Zhao Yongming
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1003) prefetch: the config file
Posted by "Zhao Yongming (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhao Yongming updated TS-1003:
------------------------------
Component/s: Configuration
Description: PreFetch and Update is the most strange plugin that keep in the proxy dir. and we have some PreFetch API that should make some usage, but the config file for prefetch and configs not managed live other config files in the tree. we should make PreFetch a big feature for TS, and smooth all the ugly coded issue.
Fix Version/s: (was: 3.1.4)
2.1.3
when dealing with the config file and config options updates, I think we need figure out some of the issues later:
1, how to deal with configs that our plugins need:
1.1, how to add config file to the mgmt system. the config file is monitored by mgmt, and the file list is hard coded into fileUpdated(), that will show no flex while the config file keeping increasing for now.
1.2, how to deal with the config option call backs? is there any guide in the coding?
2, should we bring up the config file syntax talk?
2.1, why so many types and so many codes in handling these syntaxes?
I think we need some roadmap on the configs, at least some directons :D
> prefetch: the config file
> -------------------------
>
> Key: TS-1003
> URL: https://issues.apache.org/jira/browse/TS-1003
> Project: Traffic Server
> Issue Type: Sub-task
> Components: Configuration
> Reporter: Zhao Yongming
> Assignee: Zhao Yongming
> Fix For: 2.1.3
>
>
> PreFetch and Update is the most strange plugin that keep in the proxy dir. and we have some PreFetch API that should make some usage, but the config file for prefetch and configs not managed live other config files in the tree. we should make PreFetch a big feature for TS, and smooth all the ugly coded issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1003) prefetch: the config file
Posted by "Zhao Yongming (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhao Yongming updated TS-1003:
------------------------------
Attachment: TS-1003.patch
here is the patch that will make the config same as other.
> prefetch: the config file
> -------------------------
>
> Key: TS-1003
> URL: https://issues.apache.org/jira/browse/TS-1003
> Project: Traffic Server
> Issue Type: Sub-task
> Components: Configuration
> Reporter: Zhao Yongming
> Assignee: Zhao Yongming
> Fix For: 2.1.3
>
> Attachments: TS-1003.patch
>
>
> PreFetch and Update is the most strange plugin that keep in the proxy dir. and we have some PreFetch API that should make some usage, but the config file for prefetch and configs not managed live other config files in the tree. we should make PreFetch a big feature for TS, and smooth all the ugly coded issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1003) prefetch: the config file
Posted by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1003:
------------------------------
Fix Version/s: (was: 3.1.5)
3.3.0
Moving this out to 3.3.0, please move back to 3.1.4 if this will be worked on *soon*. Also, take a look at what can be closed here please!
> prefetch: the config file
> -------------------------
>
> Key: TS-1003
> URL: https://issues.apache.org/jira/browse/TS-1003
> Project: Traffic Server
> Issue Type: Sub-task
> Components: Configuration
> Reporter: Zhao Yongming
> Assignee: Zhao Yongming
> Fix For: 3.3.0
>
> Attachments: TS-1003.patch
>
>
> PreFetch and Update is the most strange plugin that keep in the proxy dir. and we have some PreFetch API that should make some usage, but the config file for prefetch and configs not managed live other config files in the tree. we should make PreFetch a big feature for TS, and smooth all the ugly coded issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-1003) prefetch: the config file
Posted by "Zhao Yongming (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhao Yongming resolved TS-1003.
-------------------------------
Resolution: Fixed
commit a4e4a69c14d32cf9e52bd367682189011f2468ac
> prefetch: the config file
> -------------------------
>
> Key: TS-1003
> URL: https://issues.apache.org/jira/browse/TS-1003
> Project: Traffic Server
> Issue Type: Sub-task
> Components: Configuration
> Reporter: Zhao Yongming
> Assignee: Zhao Yongming
> Fix For: 3.3.1
>
> Attachments: TS-1003.patch
>
>
> PreFetch and Update is the most strange plugin that keep in the proxy dir. and we have some PreFetch API that should make some usage, but the config file for prefetch and configs not managed live other config files in the tree. we should make PreFetch a big feature for TS, and smooth all the ugly coded issue.
--
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
[jira] [Updated] (TS-1003) prefetch: the config file
Posted by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1003:
------------------------------
Fix Version/s: (was: 2.1.3)
3.1.3
Changing target version (I assume it was supposed for 3.x and not 2.x :)
> prefetch: the config file
> -------------------------
>
> Key: TS-1003
> URL: https://issues.apache.org/jira/browse/TS-1003
> Project: Traffic Server
> Issue Type: Sub-task
> Components: Configuration
> Reporter: Zhao Yongming
> Assignee: Zhao Yongming
> Fix For: 3.1.3
>
> Attachments: TS-1003.patch
>
>
> PreFetch and Update is the most strange plugin that keep in the proxy dir. and we have some PreFetch API that should make some usage, but the config file for prefetch and configs not managed live other config files in the tree. we should make PreFetch a big feature for TS, and smooth all the ugly coded issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira