Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  29 Sep 2004, Stefan Ritt, Info, Increased number of clients in midas.h, important! 
    Reply  03 Oct 2004, Konstantin Olchanski, Info, Increased number of clients in midas.h, important! 
       Reply  03 Oct 2004, Stefan Ritt, Info, Increased number of clients in midas.h, important! 
          Reply  03 Oct 2004, Konstantin Olchanski, Info, Increased number of clients in midas.h, important! 
             Reply  04 Oct 2004, Stefan Ritt, Info, Increased number of clients in midas.h, important! 
                Reply  08 Oct 2004, chris pearson, Info, Increased number of clients in midas.h, important! 
                   Reply  08 Oct 2004, Konstantin Olchanski, Info, Increased number of clients in midas.h, important! 
Message ID: 151     Entry time: 03 Oct 2004     In reply to: 149     Reply to this: 152
Author: Stefan Ritt 
Topic: Info 
Subject: Increased number of clients in midas.h, important! 
> Stefan, to avoid confusion from crashes caused by incompatible ODBs would it be possible to add a "version number" to ODB,
together with a check and an error message 
> saying "oops... incompatible ODB, please rebuild your programs"? We tend to have different versions of midas floating around and
users have old executables stashed away, 
> and all this makes it rather difficult to manually keep track on what ODB is compatible with what midas.

I fully agree that a version number in ODB is a good thing, and I certainly will put one there, but this won't help for old
applications. If I add new code which checks in cm_connect_experiment() if the version number matches, this will only help for new
applications connecting to old ODBs. If old applications (prior to invention of the version number) connect to a new ODB, they still
will crash.

However, we are planning to make a new release 1.9.5 soon (next week), so can can people tell not to "mix" 1.9.5 with pre-1.9.5
programs.
ELOG V3.1.4-2e1708b5