![]() ![]() ![]() |
![]() |
|
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Return to Case Study In this paper we discuss our ongoing experience in integrating a Product Data Management application, ThinkTeam, and the Siena Publish/Subscribe Middleware. This integration should support ThinkTeam users in managing the lost-update problem. This problem arises when a client performs a check-out/modify/check-in cycle on a document that may be used as reference copy by other clients. In this context Siena should allow for disseminating alerts about the state of the document. The integration between ThinkTeam, and Siena poses new requirements on how to manage events and subscriptions. The paper discusses a set of integration problems and their possible solutions. ![]() ©2005 Association for Computing Machinery |