Hi Jens,
I know you scenario well, so I here the differences If found so far :
- shared subproject
- definitely read only, no matter what permission the user has
- there will be no "incomming change" visible in case there are newer revision available.
- frozen shared member
- the share is by default by-directional. so given the right permissions the user can checkin and create new revisions of the member (effecting the source of the share). The freeze only prevents the user from updating the member revision used in his (target) project.
- in case there are newer revision available, this will be visible on the frozen share (might be confusing especially in IDEs)
- as long as not specially defined the Freeze/Thaw permissions are inherited from the shared archives ACL. This might lead to very mixed ACLs in one project.
HTH Matthias