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
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
