On Tue, 10 Sep 2002, Roger Turk <[EMAIL PROTECTED]> wrote:
> With all the important things that needs to be addressed in Arachne, the > appearance of a little, insignificant "X" doesn't come close to making the > list! > We need: > *** Access to secure sites! (No. 1 priority) > *** Javascript capability. (Only because so many sites use it.) > Until these are addressed, not one second should be devoted to how an "X" > appears. Roger..et al, Yes...temporarily 1.71pre kills 95% of the httpsPhonies...but we DO need the SSL support....and....Javasjunk is becoming ubiquitous and that support is also needed. 1.71pre is a vast improvement over both 1.69 (which I use mostly) and 1.70r3 (which I WOULD use mostly, if it weren't for that DownloadLoop bug). With the httpsSpoof technique expanded to "shell-out" to a DOS DPMI OpenSSL Engine....true Secure (HTTPS) capability should be able to be added to Arachne as a plug-in....we already have this general procedure working when Arachne "shells-out" to use CWDPMI to handle images....it should be able to be adapted to running an SSL plug-in, also. With the IgnoreJS/httpsSpoof "shell-out-to-CWDPMI" technique/procedure working, we should be able to either adapt the Linux "SpiderMonkey" JS Engine to Arachne...or adapt the orginal DOS JS Engine (I have it, but can't remember the name) to be used as an Arachne plug-in.... I think the key point is to keep on using the "shell-out" technique that Michael adopted for image handling, so that all improvements are added as plug-ins rather than compiled into CORE.EXE....making it bloat up to (horrors..!!!!) windgedozzz style...<g> ....gregy -- This mail was written by user of Arachne, the Ultimate Internet Client
