Hi Juha,
Yep, that was my initial view on fixing this issue, but I'm wondering if
it pays the effort, mainly because:
1) putting the domain list in core, with the reload functionality,
will raise again sync problems
2) usually general solutions are more complicate (volume of work)
Bogdan-Andrei Iancu writes:
3) for the moment the only need for domain list in core is because
of rr-domain interaction, so not sure if a general solution is really
needed..
exactly. if rr module needs domain, it can very well get them from
domain module using the api it provides.
Hi Juha,
The idea was to have all modules using a core function (like rr does
now) to check is a domain is local IP or domain, instead of having each
module to use a core function and a function from other module (domains)..
Regards,
Bogdan
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
Bogdan-Andrei Iancu writes:
The idea was to have all modules using a core function (like rr does
now) to check is a domain is local IP or domain, instead of having each
module to use a core function and a function from other module
(domains)...
in that case, domain module should also
Hi Juha,
As I suggested during the IRC meeting the multi-domain issue with RR may
be solved in two ways:
1) import the domains into the aliases list in core (RR already uses
this list)
2) make a special dependency between RR and DOMAINS
1) has the advantage of being more general - the
Bogdan-Andrei Iancu writes:
2) technically simple, but solves only the particular case of RR module;
and there will be no common way to check from script/other modules if
some domain is local or not.
bogdan,
i don't understand. the api that domain module provides for other
modules IS a
there was also irc discussion on making rr module check if a domain in
route uri is local. i recently implemented in domain module capability
to check from other modules if domain is local:
domain_api_t domain_api;
bind_domain_t bind_domain;
bind_domain = (bind_domain_t)find_export(bind_domain,
