![]() (Note that Skype consumer service uses a completely different back end that was built independently when Skype was it's own company.) Rearchitecting the entire product ecosystem is not feasible. This has been true since the original Office Communicator product, and the entire ecosystem is built around the architecture. The fundamental problem is that Office Communicator/Lync/Skype for Business conversation model is session-based, not people-based, so every conversation between two people is distinct and stored independently in the conversation history in Exchange. Since this has been a long-running discussion, and people have asserted various solutions over time, I will offer some context on the issue and our efforts to resolve it. ![]() This does not prevent multiple entries in the Chats list for the same contact. ![]() ( Show conversations in separate windows is enabled in Preferences, or you have double-clicked an item in chats to pop out a window.) In this case, we will reuse the same, open window for all conversations with that contact. In the latest Insider release, we have an improvement that prevents multiple windows if a conversation is open in a separate window. We are not ignoring the issue, nor are we declining to fix it because of Teams. Unfortunately, the timeline for a fix that I had original expected has not worked out. I know that this is a frustrating experience in the UI. First, let me say 'thanks' to everyone for patience on this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |