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 2011/01/25 01:42:43 UTC

[jira] Updated: (TS-84) code base: PATH_NAME_MAX vs PATH_MAX

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

Leif Hedstrom updated TS-84:
----------------------------

    Fix Version/s:     (was: 2.1.6)
                   3.1

Moving out to v3.1, I think we can address this issue later, since it doesn't affect any public APIs directly.

> code base: PATH_NAME_MAX vs PATH_MAX
> ------------------------------------
>
>                 Key: TS-84
>                 URL: https://issues.apache.org/jira/browse/TS-84
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Cleanup
>    Affects Versions: 2.0.0a
>         Environment: All
>            Reporter: George Paul
>            Priority: Minor
>             Fix For: 3.1
>
>
> Originally PATH_NAME_MAX was to be used for PATH_MAX for portability between OS's AFAIR. PATH_MAX is inconsistent  on various OSs (linux-4096, osx/bsd-1024, windows-260(?), etc). TS is more consistent in the use of PATH_NAME_MAX in the code base (cache, hostdb, plugins, etc) while TM is not as consistent. TC never used it. The code base needs to examined for usage of both and made consistent and portable. The current suggestion is to use what TS currently uses which is PATH_NAME_MAX. This should be revisited when this issue is worked on. 
> -George

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.