This is a consequence of an early design decision to cache all documents for the current session, which had the performance advantage of eliminating having to fetch them again, and made it easy to retain changes such as forms input. We would have liked to be able to provide SSL encryption support, but this would be problematical for two reasons. Firstly, there would be technical problems interfacing SSL support routines, written in C, with the existing Charlotte code which uses REXX and CMS Pipelines. Secondly, there would probably be license problems, as it would presumably be necessary to pay to use the SSL implementation, but Charlotte itself is currently free. Jonathan hit on the bad points.
Charlotte is fast, easy and intuitive to use.
She was becoming increasingly frustrated with Netscape, so I suggested she try using Charlotte. It's very easy to use Charlotte. Eg. while waiting for more data to arrive, format what has already arrived. I'd better wrap it up. I strongly believe that VM has a very important role to play on the Web.