On Mon, Feb 18, 2013 at 5:29 PM, Bruce Perens <[email protected]> wrote:
> I think the community is still small and localized enough that we can > have a flag day. We will announce that after a certain date we expect > everyone to use the new binary on the air. > > This time. We need a better method next time. I think the ham situation is rather different from non-ham, and the situation also depends on where in the stack you have an incompatibility. The recent problem was kind of analogish; a version number wouldn't have helped. Loading different versions of the library depending on the date of connection initiation could work out well. The library version number could even be set to the switchover date. For example, a libfoo.so.2013.4.18 would replace prior versions on that date. This does require insisting that the library be loaded via dlopen or similar. Also, insist on UTC! Note that apps supporting more than one connection would need to have more than one library loaded until all the old connections are terminated. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
