[Chandler-dev] Chandler sharing TCP and SSL usage
grant at osafoundation.org
Tue Jul 25 10:58:09 PDT 2006
On 24 Jul, 2006, at 15:32, Grant Baillie wrote:
>> The summary is that there are a bunch of TCP/SSL issues to
>> investigate on the Chandler side first.
>> 1) There are 7 separate SSL connections during Publish. Only 1
>> should really be needed. An ignorant guess is we'd be using
>> PyOpenSSL classes in different places, instantiating new and
>> separate objects rather than passing one around (or looking one
>> up) to handle the sharing traffic.
> 1 extra connection occurs because Chandler uses separate
> connections for the CalDAV (all the .ics files) & Chandler-specific
> (the .chandler subdirectory) shares. This isn't necessary, and also
> adds roundtrips because we're not using information learned earlier
> (like, the fact that .chandler/ exists).
FWIW, I figured out 2 more, because the Sharing code makes separate
connections to determine what your server supports (in Sharing.publish
()), and to find a unique collection name to share to
More information about the chandler-dev