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 2010/06/17 18:06:24 UTC
[jira] Created: (TS-392) Support (or remove)
WITH_DETAILED_VCONNECTION_LOGGING
Support (or remove) WITH_DETAILED_VCONNECTION_LOGGING
-----------------------------------------------------
Key: TS-392
URL: https://issues.apache.org/jira/browse/TS-392
Project: Traffic Server
Issue Type: Improvement
Reporter: Leif Hedstrom
Priority: Minor
There's an #ifdef WITH_DETAILED_VCONNECTION_LOGGING which is always "disabled" in the code. This feature depends on DetailedLog.{cc,h}, and in fact, it's the only piece in the code that uses this DetailedLog class.
I'd suggest two possible improvements
1) Make WITH_DETAILED_VCONNECTION_LOGGING ./configure settable (this is assuming we need / want this detailed log feature for vconnections). If we do this, then compiling DetailedLog.cc should be conditional on this option being enabled.
2) Remove this feature, and the supporting code, entirely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-392) Support (or remove)
WITH_DETAILED_VCONNECTION_LOGGING
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-392:
-----------------------------
Fix Version/s: 2.1.2
> Support (or remove) WITH_DETAILED_VCONNECTION_LOGGING
> -----------------------------------------------------
>
> Key: TS-392
> URL: https://issues.apache.org/jira/browse/TS-392
> Project: Traffic Server
> Issue Type: Improvement
> Reporter: Leif Hedstrom
> Priority: Minor
> Fix For: 2.1.2
>
>
> There's an #ifdef WITH_DETAILED_VCONNECTION_LOGGING which is always "disabled" in the code. This feature depends on DetailedLog.{cc,h}, and in fact, it's the only piece in the code that uses this DetailedLog class.
> I'd suggest two possible improvements
> 1) Make WITH_DETAILED_VCONNECTION_LOGGING ./configure settable (this is assuming we need / want this detailed log feature for vconnections). If we do this, then compiling DetailedLog.cc should be conditional on this option being enabled.
> 2) Remove this feature, and the supporting code, entirely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-392) Support (or remove)
WITH_DETAILED_VCONNECTION_LOGGING
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-392:
-----------------------------
Assignee: Leif Hedstrom
> Support (or remove) WITH_DETAILED_VCONNECTION_LOGGING
> -----------------------------------------------------
>
> Key: TS-392
> URL: https://issues.apache.org/jira/browse/TS-392
> Project: Traffic Server
> Issue Type: Improvement
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.1.2
>
>
> There's an #ifdef WITH_DETAILED_VCONNECTION_LOGGING which is always "disabled" in the code. This feature depends on DetailedLog.{cc,h}, and in fact, it's the only piece in the code that uses this DetailedLog class.
> I'd suggest two possible improvements
> 1) Make WITH_DETAILED_VCONNECTION_LOGGING ./configure settable (this is assuming we need / want this detailed log feature for vconnections). If we do this, then compiling DetailedLog.cc should be conditional on this option being enabled.
> 2) Remove this feature, and the supporting code, entirely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-392) Support (or remove)
WITH_DETAILED_VCONNECTION_LOGGING
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-392:
-----------------------------
Component/s: Network
> Support (or remove) WITH_DETAILED_VCONNECTION_LOGGING
> -----------------------------------------------------
>
> Key: TS-392
> URL: https://issues.apache.org/jira/browse/TS-392
> Project: Traffic Server
> Issue Type: Improvement
> Components: Network
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.1.2
>
>
> There's an #ifdef WITH_DETAILED_VCONNECTION_LOGGING which is always "disabled" in the code. This feature depends on DetailedLog.{cc,h}, and in fact, it's the only piece in the code that uses this DetailedLog class.
> I'd suggest two possible improvements
> 1) Make WITH_DETAILED_VCONNECTION_LOGGING ./configure settable (this is assuming we need / want this detailed log feature for vconnections). If we do this, then compiling DetailedLog.cc should be conditional on this option being enabled.
> 2) Remove this feature, and the supporting code, entirely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TS-392) Support (or remove)
WITH_DETAILED_VCONNECTION_LOGGING
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-392.
------------------------------
Resolution: Fixed
Closing, there is now a new option to configure, --with-detailed-log
> Support (or remove) WITH_DETAILED_VCONNECTION_LOGGING
> -----------------------------------------------------
>
> Key: TS-392
> URL: https://issues.apache.org/jira/browse/TS-392
> Project: Traffic Server
> Issue Type: Improvement
> Components: Network
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.1.2
>
>
> There's an #ifdef WITH_DETAILED_VCONNECTION_LOGGING which is always "disabled" in the code. This feature depends on DetailedLog.{cc,h}, and in fact, it's the only piece in the code that uses this DetailedLog class.
> I'd suggest two possible improvements
> 1) Make WITH_DETAILED_VCONNECTION_LOGGING ./configure settable (this is assuming we need / want this detailed log feature for vconnections). If we do this, then compiling DetailedLog.cc should be conditional on this option being enabled.
> 2) Remove this feature, and the supporting code, entirely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.