On 02/04/2010 12:31 PM, Jason wrote:
I'd like to voice a comment,${prefix}/ts seems somewhat vague unless you were going to rename all the scripts ts. My eyes can read quite clear exactly what this header is even if i had no idea what trafficserver was and just happened to be reading some random piece of code: "#include<trafficserver/sdkapi.h>"
I'm not sure I understand why the two include files (which would be used by a very small minority of TS users, those who actually implements new plugins, or debug existing plugins) should have any impact on what the names of the scripts or "binaries" are? That much said, I can certainly understand the argument for "readability" for the common user, but do we care about that for these low level APIs?
My personal thought for suggesting /ts/ was to keep it short and clean in the "namespace".
Cheers, -- Leif
