[Chandler-dev] Chandler sharing TCP and SSL usage

[Heikki Toivonen]

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
> (Sharing.getExistingResources()).

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?

-- 
  Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060725/17fabc26/signature.pgp