The remoteId parameter is determined by the sending instance. However, how can uniqueness on the receiving side be guaranteed if multiple sending instances provide the same remoteId? To solve this, the remoteId should be generated by the receiving instance instead and be accessible via a GET operation on /cloud/shares and upon share offer creation.
The
remoteId
parameter is determined by the sending instance. However, how can uniqueness on the receiving side be guaranteed if multiple sending instances provide the sameremoteId
? To solve this, theremoteId
should be generated by the receiving instance instead and be accessible via aGET
operation on/cloud/shares
and upon share offer creation.