Lotus Instant Messaging/ Web Conferencing ... - IBM Redbooks

users on the system was not shown, either in terms of the number of IM sessionsor the amount of traffic within those sessions. It would have been possible toshow on the graph (perhaps by the thickness of the lines) the number of sessionsbetween two users, but to encourage people to use the system, this data was notshown.Any future development of VS will have to seriously consider privacy implicationsso that people will be willing to use the system.Future improvements►►►►►Adapting the VS server to use the Intelligent Miner Modelling 8.1 for dataaggregation (rather than custom aggregation algorithm)Securing functionality to prevent data spoofingSetting up a temporal element to show IM traffic between specific timesAutomatic social network analysisIncreased privacy protectionLessons learnedAlthough VS is intended as a proof of concept system, a number of lessons werelearned regarding the building of Sametime-enabled applications.1. Users do not expect to lose any functionality that exists in theSametime-based client they are currently using. Even in situations where theadditional features far outweighed any loss, users still demanded all thefunctionality of their existing system.2. Applications using Sametime functionality are likely to be left running on theuser’s desktop permanently and, therefore, need to be as lightweight aspossible. The resources used by the VS client has posed a problem to someusers. The overhead was mainly caused by the association graphingfacilities.3. Privacy is a big issue for people using custom Sametime applications andneeds to be thought of while designing any Sametime-based application.4. Careful use of threading needs to be used in applications built with Sametimecomponents in. It is important that the surrounding application does not holdup the Sametime elements, as delays can be annoying to users.454 Lotus Instant Messaging/Web Conferencing (Sametime): Building Sametime-Enabled Applications