Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)



Hi there,

On Thursday 05 August 2010 Matthew Barnes wrote:
> On Thu, 2010-08-05 at 18:30 +0200, Christian Hilberg wrote:
> > Result: While libsoup should build against the current GnuTLS lib
> > (development version, 2.11.0), which has PKCS #11 support since a few
> > weeks now, libsoup has no infrastructure for handling client
> > certificates at all [1] and GnuTLS does not seem to handle that by
> > itself the way NSS does.
> Hmm, then perhaps CamelHttpStream might be a good stopgap after all.  Be
> aware that I have marked it as deprecated and do still plan to remove it
> after we transition to WebKit, but perhaps by then Dan's TLS work for
> GIO will have landed.

Since we are developing against Evo 2.30, my thoughts are the same. I'll try 
to wrap up CamelHttpStream usage in a way that should make it easy (hopefully) 
to replace CamelHttpStream by some true HTTP lib later on.

Thanks and kind regards,

	Christian

-- 
kernel concepts GbR        Tel: +49-271-771091-14
Sieghuetter Hauptweg 48    Fax: +49-271-771091-19
D-57072 Siegen
http://www.kernelconcepts.de/

Attachment: signature.asc
Description: This is a digitally signed message part.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]