[Chandler-dev] Chandler sharing TCP and SSL usage
heikki at osafoundation.org
Tue Jul 25 12:00:49 PDT 2006
Grant Baillie wrote:
> 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
Could we cache the server capabilities?
Could we try to publish to some name with the condition that it will
fail if that name already exists, and retry with different name if so?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 251 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060725/17fabc26/signature.pgp
More information about the chandler-dev