X-Git-Url: http://www.lcore.org/git/lcore.git/blobdiff_plain/d8d568ba2b45905cbe2c8e1956b6444d5b6560f4..2579cad7a973072619a7fc17ff6af9cc75264972:/lcoreconfig.inc?ds=inline

diff --git a/lcoreconfig.inc b/lcoreconfig.inc
index 27b6e82..cda6ec7 100644
--- a/lcoreconfig.inc
+++ b/lcoreconfig.inc
@@ -12,6 +12,7 @@ to disable, undefine it here, or define "noipv6" in the app}
 {$define ipv6}
 {$endif}
 
+{-------------------------------------------------------------------------------------}
 {there are 2 ways to use DNS in lcore: dnscore, which an entire built in DNS client, and getaddrinfo.
 dnscore is always included on *nix to avoid libc dependency problems, but getaddrinfo is used on windows.
 when getaddrinfo is used, there is no reason to include dnscore, and it increases the exe size,
@@ -19,6 +20,14 @@ unless you want to use custom nameserver addresses. enable this setting to alway
 
 {-$define syncdnscore}
 
+{-------------------------------------------------------------------------------------}
+{lcore contains a built in general purpose secure random number generator, which is used elsewhere in lcore, for
+example by the DNS resolver. the used random function can be hooked to point to one's own RNG as desired.
+it is then also possible to not include the built in RNG in the exe, which reduces code size}
+
+{-$define nolcorernd}
+
+{-------------------------------------------------------------------------------------}
 {on windows up to XP, listening on ipv6 will not listen on ipv4, while on other platforms it does, 
 so a single listener cant get all connections for a port number, only those for one address family.
 also it means a portable app would gave to deal with inconsistent behavior.
@@ -27,3 +36,5 @@ enable this option to simulate the behavior of listening on both v4 and v6}
 {$ifdef win32}{$ifdef ipv6}
 {$define secondlistener}
 {$endif}{$endif}
+
+{-------------------------------------------------------------------------------------}
\ No newline at end of file