On Fri, Jul 29, 2016 at 5:18 PM, Jan Just Keijser <[email protected]> wrote: > another remark: making this option CCD-file specific a good idea, but how > you do ensure that the server only applies it to this particular client? > o->ncp_enabled seems a global at first glance. Consider this scenario: > > 1) client A connects , for which we want to disable NCP; hence a > client-connect script or CCD file with 'ncp-disable' in it; > 2) client B connects, no CCD file, it's running v2.4+, so we want NCP. > > How does the server handle this? Or did I miss the "per-client options" > struct?
You've just answered your own question ;) The ccd file parsing operates on mi->context.options, which is a connection-specific options struct (mi = 'multi instance'). See multi_connection_established(). -Steffan
