4 Dec
2008
4 Dec
'08
2:37 p.m.
On Thu, Dec 04, 2008 at 11:11:03AM +0000, Jeremy Henty wrote:
Opening the authentication dialog runs the FLTK event loop, which means that incoming data can call the cache again, triggering CCC warnings. We work around it by deferring the dialog to a timeout so that the cache finishes iterating over the clients before the dialog appears. This is annoying but I don't see a better way at the moment.
Have you thought about how other protocols can be integrated with this? Examples are: - TLS with client side authentication or verification for the server certificate - non-anonymous FTP Joerg