If your server is single-threaded or forking, that should be enough. If your server needs to be multi-threaded, you will run into problems with SSL misbehaving under threads.
I ended up writing a multiplexed (single-threaded server) directly on top of IO::Socket::SSL, inside a module which gets passed a Thread::Queue handle so that the work for each connection can be farmed out to other threads.
I got some help here with the mutliplexing HTTPS server, so do a super-search and you'll find a working example.
-David
In reply to Re^3: Soap::lite - https ?
by erroneousBollock
in thread Soap::lite - https ?
by ethrbunny
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |