(another) WebKit port of Browse

[Asheesh Laroia]

I've snipped away the parts I have no comment on, but:

On Mon, 7 Jul 2008, Martin Langhoff wrote:

> Well, there is quite a bit of thinking that needs to happen here, and I 
> am working on something else at the moment. So, these are quick notes

And me, too - just quick notes:

> - XS installs/deployments will be done in so many different scenarios 
> that we cannot address the promises needed the conventional PKI 
> infrastructure. We need a good strategy to sidestep the PKI requirements 
> of full blown SSL. A few weird schemes come to mind, all nasty :-)

I'd be interested to hear them.

> - SSL overhead at the network layer is very significant. Network 
> bandwidth and latency on the local link are valuable resources.

Do it once at authentication time and use an HTTP cookie after that (that 
is available to HTTP sites in the same doamin).

> - SSL CPU overhead at the XS end is moderately significant.

Same answer as above.

-- Asheesh.

-- 
Life is a grand adventure -- or it is nothing.
 		-- Helen Keller