mworks/mworks — pull request #1 by davidcox (2012-02-02 16:13:30+00:00)
Title: Conduit clock offset

We recently ran into a problem where we had some timebase confusion surrounding MW events on either side of an interprocess conduit. Basically, since MW now references time relative to session start (rather than epoch), the MW instances on either side of a conduit will have different ideas about what time is "0."

The changes included in this pull request provide machinery for the conduits to communicate this timebase information automatically, and to correct it on the fly (this can optionally be turned off, so that events retain the timebase from the "remote" side of the conduit). The default option is currently to do the correction (such that events always arrive timestamped with the correct "local" time), though I could be convinced that the default should go the other way. I'm not sure if other are using the conduits yet, but this could be important if they are assuming the old behavior.

I'm doing this as a pull request to increase visibility of the changes, and to provide a forum for discussion of the changes prior to integration. For anything other than small changes and bug-fixes, I think this probably a good way to manage things.