> >So using the protocols as they exist today, each HTTPS-enabled domain > >requires its own IP address. > > Not quite true. They can be done via different ports on the same IP. > Not so easy on a Cobalt though.
You are right. Running a separate Apache process for each domain, listening on a different port, is possible. But yeah, on a Cobalt (or any "low RAM" server) it's probably not the easiest thing to attempt. Plus, with non-standard ports, it wouldn't be easy just for people to connect to the server -- invariably the port number gets left off the URL... _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
