SSL support is one of the biggest lacks in dillo for me. To that end, I'm thinking of adding it in. Without knowing the dillo codebase, I see two obvious options: 1) Add a src/IO/https.c file based on src/IO/http.c 2) Move http.c to using openssl's BIO's which can support either encrypted or clear traffic, as well as filters. I think the dpi is, in favor of design, the best solution. I am no
Thu, 13 Mar 2003 15:51:09 -0800: Ami Fischman <usenet@fischman.org> programmer, so don't count that much on me. But i have another idea. What about implementing every protocol as dpi? currently the dpi looks, for me as simple user: dpi:/bm/ but why not implementing it as bm://, so http:// would call the http-dpi, ftp:// would call the ftp-dpi, ... This would create a complete module-based client and dillo can be focused on displaying. http:// could be not much more than a wrapped wget, or i am wrong and this whole scheme is impossible? -- Andreas Zwinkau (andi.dasstellenwirinsinternet.de)