Re: Adding userTag to epicsTimeStamp

["Kasemir, Kay" <kasemirk@ornl.gov>]

>Not saying that this specific tag should not be 64 bits wide, but to change an existing approved design,
>I would like to see a minimum amount of justification and discussion.

A time tag change from 32 to 64 bits makes no difference to those who simply use pvAccess via qsrv/pvaSrv since the EPICS database never provided a value, anyway.

And even though the time stamp is part of most updates, if I understand correctly this change will hardly affect the network package size because when you leave the tag at its default value of 0 and don't change, the monitor deltas won't include the tag, only the secs & nanosecs, correct?

The SNS beam line neutron data does use the user tag for a sequence number, incremented by server to allow double-checking for missing updates. So our software might need to be updated. I believe this could be done beam line by beam line, won't be a show stopper.

-Kay