Feature #401

DDR for services

Added by Madars Vitolins 4 months ago. Updated about 1 month ago.

Status:NewStart date:03/25/2019
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


We could add:

# This will make each ATMI client/server to parse ndrxconfig.xml

Then we could have "<services>" tag and "<routing>". the groups could be numberic (like rmid).

for these special services, we could advertise them with "<service_name>,<group_id>".
Thus if user makes "tpadvertise"/"tpunadvertise" we could use "rmid" and make two advertise calls one for common services and another for group shared.


#1 Updated by Madars Vitolins 4 months ago

The rules for services we could store in RWLOCKED shard memory and in tpcall we could check the SHM and rules stored there.

#2 Updated by Madars Vitolins 4 months ago

we could add xadmin command like;

xadmn reload
xadmin ddr_reload

so that ndrxd locks the SHM with write lock and installs there new rules.

#3 Updated by Madars Vitolins about 1 month ago

Service auto transactions shall be supported too.
Thus we need:

- SVCTIMEOUT (with out kill at the moment)

Also available in: Atom PDF