Feature #401

DDR for services

Added by Madars Vitolins about 1 year ago. Updated 5 months ago.

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

0%

Category:-
Target version:-

Description

We could add:

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

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.

History

#1 Updated by Madars Vitolins about 1 year 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 about 1 year 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 12 months ago

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

- SVCTIMEOUT (with out kill at the moment)
- AUTOTRAN
- TRANTIME

#4 Updated by Madars Vitolins 9 months ago

ndrxd whould copy the rules to shared memory block, from start to finish (with RWLOCK installed). Binaries at tpinit point, would read the shared mem blocks, compile the rules and build the in-memory hash list of services. Then at tpadvertise or tpcall/tpforward/connet point we lookup the hash list, check the rules and detect the target group.

#5 Updated by Madars Vitolins 5 months ago

It would be nice to have to fallback services to some other, if in found routing group services does not exist.

Also available in: Atom PDF