Hello,
I am thinking to re-add AOL3.x style of binder where it forks and
accepts binder requests during server startup. For now i just re-added
binder process and introduced new public function
Ns_SockBinderListen(int type, char *address, int port, int options)
which allocates socket directly from binder. All standard functions
works as normal which means for now specific modules who call new
functions will use new binder API.
I will test it and then may be it can be added into all Ns_SockListenXXX
family so we will not need -b arg anymore. It is hard to administer and
perform automatic re-configuration with 2 completely different places
where ports can be defined.
Are there any objections?
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
