Shark Locking

Has anyone looked into the Shark locking mechanism that would prevent
two users from working on the same activity?

I can to map my external user groups to an individual Shark id.  But, if
two different people in a single external group try to access Shark,
they'll both be mapped to the same Shark ID (since they belong to the
same group).  

To Shark, it appears the same person is logging in twice and I don't
think it will prevent both users from working on the same activities.

Is this thinking correct?

I believe I could avoid this question all together if I used Shark's
user groups and created my own AssignmentManager but I can't do that
because the AssignmentManager interface only passes in UserIDs and does
not allow Shark Groups to be passed in.

Greg
******* Confidentiality Notice *******
This email, its electronic document attachments, and the contents of its website linkages may contain confidential health information.  This information is intended solely for use by the individual or entity to whom it is addressed.  If you have received this information in error, please notify the sender immediately and arrange for the prompt destruction of the material and any accompanying attachments.

--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws