session: connects seg manager is always first 46/32246/10
authorFlorin Coras <fcoras@cisco.com>
Thu, 6 May 2021 22:32:14 +0000 (15:32 -0700)
committerDamjan Marion <dmarion@me.com>
Fri, 7 May 2021 10:46:20 +0000 (10:46 +0000)
commit94a6df005d9e94f3b836ad3c93d1464b4a840499
treec55259ac6ce0e373abf7633353c29ad74e305b26
parentbd376a8ce8425f45b23074398949e8055de29280
session: connects seg manager is always first

By convention, connects segment manager will be first. Therefore it will
be the one with the first segment wherein lies the app's message queue.

Saves us the trouble of allocating it on first connect, if app started
by listening, and we no longer need to track if it's assignable to a
listener or if it can be removed.

Type: improvement

Signed-off-by: Florin Coras <fcoras@cisco.com>
Change-Id: Iba9a8ffaab618eeb41ec2144dcfee62d006dc7a2
src/plugins/hs_apps/http_server.c
src/plugins/hs_apps/proxy.c
src/plugins/http_static/static_server.c
src/plugins/quic/quic.c
src/plugins/unittest/session_test.c
src/vnet/session/application.c
src/vnet/session/application.h
src/vnet/session/application_worker.c
src/vnet/tls/tls.c