query_module: configurable query processing modules
Current API provides a "query plan" for each zone, which is basically a set of steps it needs to takes a query to be resolved. The plan is divided into several stages that reflect answer section processing. Now this query plan can be altered via configurable modules, first module is a 'synth_record' that makes synthetic forward/reverse records if the query isn't satisfied from the zone contents.
Showing
- src/Makefile.am 4 additions, 2 deletionssrc/Makefile.am
- src/knot/conf/cf-lex.l 1 addition, 3 deletionssrc/knot/conf/cf-lex.l
- src/knot/conf/cf-parse.y 14 additions, 52 deletionssrc/knot/conf/cf-parse.y
- src/knot/conf/conf.c 30 additions, 7 deletionssrc/knot/conf/conf.c
- src/knot/conf/conf.h 3 additions, 1 deletionsrc/knot/conf/conf.h
- src/knot/modules/synth_record.c 377 additions, 0 deletionssrc/knot/modules/synth_record.c
- src/knot/modules/synth_record.h 12 additions, 34 deletionssrc/knot/modules/synth_record.h
- src/knot/nameserver/internet.c 84 additions, 43 deletionssrc/knot/nameserver/internet.c
- src/knot/nameserver/internet.h 21 additions, 1 deletionsrc/knot/nameserver/internet.h
- src/knot/nameserver/process_query.c 0 additions, 6 deletionssrc/knot/nameserver/process_query.c
- src/knot/nameserver/process_query.h 2 additions, 0 deletionssrc/knot/nameserver/process_query.h
- src/knot/nameserver/query_module.c 119 additions, 0 deletionssrc/knot/nameserver/query_module.c
- src/knot/nameserver/query_module.h 124 additions, 0 deletionssrc/knot/nameserver/query_module.h
- tests/Makefile.am 2 additions, 1 deletiontests/Makefile.am
- tests/query_module.c 92 additions, 0 deletionstests/query_module.c
Loading
Please register or sign in to comment