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/03/25 17:21:15 UTC

[jira] [Updated] (TS-1182) Add a flag to LogBuffer's for endian used

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

Leif Hedstrom updated TS-1182:
------------------------------

    Fix Version/s:     (was: 3.3.4)
                   sometime
    
> Add a flag to LogBuffer's for endian used
> -----------------------------------------
>
>                 Key: TS-1182
>                 URL: https://issues.apache.org/jira/browse/TS-1182
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Logging
>            Reporter: Leif Hedstrom
>             Fix For: sometime
>
>
> After discussions with amc: To support "reading" logs (either via logcat or log collation) on a box with a different endian from where it was generated, we need to know which endian we generated the log in. Either that, or go back and do the htonl / ntohl  conversions always.  I favor the "flag", since most sane platforms are little endian anyways (certainly all platforms we support are), so why take the cost of the conversions if they are rarely used.
> This would let us check the endian flag in e.g. the log collation server, and in logcat like tools, and do the conversions only when necessary.

--
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