You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Alan M. Carroll (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/11/20 02:53:51 UTC

[jira] [Issue Comment Edited] (TS-1022) LogEntryHeader is a serialized structure but uses vague types.

    [ https://issues.apache.org/jira/browse/TS-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153641#comment-13153641 ] 

Alan M. Carroll edited comment on TS-1022 at 11/20/11 1:53 AM:
---------------------------------------------------------------

Changed LogBufferHeader and LogEntryHeader to use size specific types. Should should make the data more portable.

r1204112
                
      was (Author: amc):
    Changed LogBufferHeader and LogBufferEntry to use size specific types. Should should make the data more portable.

r1204112
                  
> LogEntryHeader is a serialized structure but uses vague types.
> --------------------------------------------------------------
>
>                 Key: TS-1022
>                 URL: https://issues.apache.org/jira/browse/TS-1022
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 3.1.0
>            Reporter: Alan M. Carroll
>            Assignee: Alan M. Carroll
>            Priority: Minor
>             Fix For: 3.1.2
>
>
> LogEntryHeader in proxy/logging/LogBuffer.h uses the type "long" and "unsigned" even though is used directly as serialized data. This means (among other things) that binary logs have different formats depending on whether ATS was built in 32 bit mode or 64 bit mode.

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