Hi, I don't really see the reason why the two policies need to be combined. Why would that be better ? Right now you have the choice which records you want to use and in which order. Once you start combining them you'll have to add config switches for that and I don't think things will get much simpler. Regards, Jan Frank Liu wrote: > Hi all, > > In the RoutingPolicy, shall we remove "srv" and include its functions > in "dns"? After all, SRV is just one of the dns types. > As we all know, dns record types includes A, CNAME, TXT, MX, SRV, etc. > Maybe we should make the "dns" routing policy to handle various dns > types directly. For example, email servers first checks dns for MX > record, if no, then it checks for A record, etc. We could make gnugk > "dns" routing policy first to check SRV record, if no, then check for > A record, then check for CNAME. > > For backward compatibility, we could leave "srv" in config for a bit, > and just treat it as "dns". > > Just a thought. > > Frank -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
