Re^4: Multiplexing HTTPS server, peer cert authentication problem.

These requirements seem pretty arbitrary. Is your server, which depends on perl, SSL libs, and a bunch of modules, really more "standalone" than Apache and some perl code? I suspect the real meaning is something like "must be easy to install and not have any licensing fees."

Unfortunately, those requirements are almost word for word from the Aceptance Criteria document, written by someone who is not me :(

Is it really that important to use non-blocking I/O

Not at all. What is important is that all requests:

are quickly, reliably accepted and serviced
are done over SSL with peer cert auth

Additionally, this must work on Windows.

-David.

Comment on Re^4: Multiplexing HTTPS server, peer cert authentication problem.

Replies are listed 'Best First'.
Re^5: Multiplexing HTTPS server, peer cert authentication problem. by perrin (Chancellor) on Mar 07, 2007 at 01:33 UTC
One thing I just remembered is that perlbal (non-blocking I/O server/proxy) works on Windows and handles SSL. You might want to see if you can adapt it to your needs. It sure seems like even IIS with CGI would be a lot simpler to get working, and meet the needs of the application.	[reply]