The 'internal' policy is quite a lot of C++ code, doing for example the longest prefix matching, round-robin routing etc. In theory you could replicate all that in an SQL stored procedure, but it would probably be at least as much code and a pain to debug. If you want the 'internal' functionality, use the 'internal' policy. ;-) Regards, Jan Edson - Lists wrote: > Which SELECT clause could be used in [Routing::Sql] to obtain the same > results gived by the internal policy ([RoutingPolicy] > default=....,internal) ? > > Edson. -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________________ 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/
