Hi, I'd like to bat around some pros / cons of selecting xinetd to implement a socket server. From my perspective the list is something like this: xinetd pros . no need to rewrite forking functionality, 'server' can be written as simple php script . forking potentially faster than php-based implementation xinetd cons . time tradeoff learning xinetd configuration vs coding in support directly in php implementation . potentially less maintainable depending on staff, likely php dev team more capable of maintaining 100% php solution Interested in your thoughts! -nathan
