|  | 
| Back
Midas
Rome
Roody
Rootana | 
| 
| Midas DAQ System | Not logged in |  |  | 
|
| 
|  01 May 2020, Joseph McKenna, Forum, Taking MIDAS beyond 64 clients |  |  01 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients |  |  01 May 2020, Pierre Gorel, Forum, Taking MIDAS beyond 64 clients |  |  02 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients |  |  02 May 2020, Joseph McKenna, Forum, Taking MIDAS beyond 64 clients |  |  02 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients |  |  02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients |  |  02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients |  |  02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients |  | 
| 
| Message ID: 1895
    Entry time: 02 May 2020
    In reply to: 1894
    Reply to this: 1896 |  | | Author: | Joseph McKenna |  | Topic: | Forum |  | Subject: | Taking MIDAS beyond 64 clients | 
 |  | 
| 
Thank you very much for feedback.
I am satisfied with not changing the 64 client limit. I will look at re-writing my frontend to spawn threads rather than 
processses. The load of my frontend is low, so I do not anticipate issues with a threaded implementation. 
In this threaded scenario, it will be a reasonable amount of time until ALPHA bumps into the 64 client limit.
If it avoids confusion, I am happy for my experimental branch 'experimental-beyond_64_clients' to be deleted.
Perhaps a item for future discussion would be for the odbinit program to be able to 'upgrade' the ODB and enable some backwards 
compatibility.
Thanks again
Joseph |