Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  01 May 2020, Joseph McKenna, Forum, Taking MIDAS beyond 64 clients 
    Reply  01 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients 
       Reply  01 May 2020, Pierre Gorel, Forum, Taking MIDAS beyond 64 clients 
          Reply  02 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients 
             Reply  02 May 2020, Joseph McKenna, Forum, Taking MIDAS beyond 64 clients 
                Reply  02 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients 
    Reply  02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients 
       Reply  02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients 
          Reply  02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients 
Message ID: 1898     Entry time: 02 May 2020     In reply to: 1897     Reply to this: 1899   1900
Author: Konstantin Olchanski 
Topic: Forum 
Subject: Taking MIDAS beyond 64 clients 
> > 
> > Does the community here have strong opinions about increasing the 
> > MAX_CLIENTS and MAX_RPC_CONNECTION limits? 
> > Am I looking at this problem in a naive way?
> > 

The issue is binary compatibility.

MIDAS has been binary compatible with itself for a long time, 20 years now, easily.

If we are to give this up, we must gain more than we lose.

On the technical level, bumping MAX_CLIENTS from 64 to 100 gives us nothing, Tomorrow an experiment
will come along asking for 101 clients. Any number you pick, it is too small for somebody. And MIDAS
already has a solution for this: edit midas.h, hit make, done.

If we are to break binary compatibility, we should go big. Remove these limits completely!

Move the MAX_CLIENTS & co fixed size arrays out of the headers in ODB and in event buffers, put
them where they can be resized as needed.

That's a binary-compatibility breaking solution I would vote for.

K.O.
ELOG V3.1.4-2e1708b5