>> My thought was, in the future, one copy of a >> server might be watching more than one port number for requests. As far >> as I know, none do that now. In that case, it could be useful for the >> server to know which port the request came in on. This seems a bit >> far-fetched, given that any 1.0-speaking client would never tell the >> server, and thus it would be assuming way too much. > > The spry server can listen to more than one port (so that you can have >SSL and HTTP/SHTTP within one incarnation of the server, sharing the same >pool of proceses, etc). I plan on extending this so that you can have >multiple configs for different interfaces all from one incarnation of the >server. EBT's DynaWeb server is capable of listening on multiple ports and also provides per-port configuration files. This is EXTREMELY useful for our customers who like to have multiple configurations (like graphical and text-only) selectable via the port number. > Its easy to keep all the fd's in an FD_SET, do a select(), and then >determine the fd that the request is coming in on. To then look up the >appropriate config is easy. Exactly! Scott Gorton Voice: (401) 421-9550 x275 Electronic Book Technologies, Inc. Fax: (401) 421-9551 One Richmond Square Email: swg@ebt.com Providence, RI 02906Received on Monday, 9 October 1995 09:32:31 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:42:56 UTC