会话线程和会话之间有什么区别? [英] What's the difference between conversationThread and conversation?

问题描述

我正在研究文档，但我不清楚Microsoft Graph(v1.0参考)上的 conversationThread 和 conversation 之间到底有什么区别?

I was investigating the documentation and it's not clear for me what exactly is the difference between conversationThread and conversation on Microsoft Graph (v1.0 Reference)?

对话的文档状态:对话是线程的集合，并且一个线程包含该线程的帖子.对话中的所有主题和帖子都共享同一主题.这种关系是主题. 在这里，我假设同一主题意味着在该对话的保护下?

The documentation for conversation states: A conversation is a collection of threads, and a thread contains posts to that thread. All threads and posts in a conversation share the same subject. The relationship is threads. Here I assume that same subject means under the umbrella of that conversation?

另一方面， conversationThread的文档指出: sessionThread是帖子的集合.最后一个帖子的收件人集合是整个主题的汇总收件人.线程可以具有越来越多的收件人集合.将收件人从该线程中删除后，会创建一个新线程.这种关系是帖子.这里不是一个线索，如果对话线程是帖子的集合，那与对话所提供的内容几乎相同吗?

In another hand, the documentation for conversationThread states: A conversationThread is a collection of posts. The last post's recipients collection is the aggregated recipients of the entire thread. A thread can have a growing collection of recipients. A new thread is created when a recipient is removed from the thread. The relationship is posts. Not a clue here, if conversationThread is a collection of posts, that's pretty much the same of what conversation offers?

我一直在尝试做什么?我正在使用Fiddler来处理HTTP请求groups/<id>/conversations和groups/<id>/threads，并且我注意到最明显的区别是threads具有isLocked属性，而conversations没有.然后我脑海中浮现出一个问题:为什么以及在什么情况下我还是会在group/<id>/conversations上使用group/<id>/threads?".也许是因为我不了解 conversationThread 和 conversation 之间的区别.

What I have been trying to do? I'm using Fiddler to play with the HTTP requests groups/<id>/conversations and groups/<id>/threads and I've noticed that the most obvious difference is that threads has a isLocked property which conversations doesn't. Then the question popped up in my mind: "Why and in which circumstances I'd be using group/<id>/threads over group/<id>/conversations anyway?". Maybe because I don't understand the difference between conversationThread and conversation.

请记住我是Microsoft Graph的新手，如果社区可以帮助我澄清这个问题，我将非常感谢.

Please bare in mind I'm a novice on Microsoft Graph and I'd really appreciate if the community could help me to clarify this question.

非常感谢！

编辑 使用Fiddler，我们设法创建了一个新线程.但是，与其按预期在指定对话中创建新线程，不如与新线程一起创建新对话. A还尝试在新创建的线程中创建新帖子，但我遇到以下错误:使用请求正文:" { "body": { "contentType": "application/json", "content": "This is a test" } }"

EDIT Using Fiddler, we've managed to create a new thread. However, rather than creating a new thread in a specified conversation as expected, it creates a new conversation to go with the new thread. A have also attempted creating a new post within the newly created thread but i am facing the following error: "The OData request is not supported" using the request body: " { "body": { "contentType": "application/json", "content": "This is a test" } }"

推荐答案

感谢您的关注并尝试使用群组对话API.我想与您分享我对您的几个问题的理解:

Thank you for your interest and trying out the group conversations API. I'd like to share my understanding with you regarding your few questions:

• "conversationThread和Microsoft Graph(v1.0参考)上的对话到底有什么区别?"

• "What exactly is the difference between conversationThread and conversation on Microsoft Graph (v1.0 Reference)?"

为什么以及在什么情况下我仍然会在group//conversation上使用group//threads?"

"Why and in which circumstances I'd be using group//threads over group//conversations anyway?"

就您可能已经读过的群组对话功能设计而言，帖子始终是某个话题的一部分，而该话题始终是某些对话的一部分.在API支持方面，API提供了会话和线程之间的奇偶校验"-方便您不需要始终引用父会话的帖子.需要明确的是，这并不意味着您可以在没有父母谈话的情况下发表帖子或话题.您只是不必每次访问现有主题或帖子时都引用父对话.我将从创建一个帖子开始: 如果您想开始发布到新对话中，为方便起见，有几种方法可以做到:

In terms of group conversation feature design, as you probably have read, a post is always a part of some thread and that thread part of some conversation. In terms of API support, the API provides "parity" between conversation and thread - the convenience of not requiring you to always reference the parent conversation for a post. Just to be clear, that doesn't mean you can have a post or thread without a parent conversation; you just don't necessarily have to reference the parent conversation every time you access an existing thread or post. I'll start with creating a post: If you want to start posting to a new conversation, there are a few ways to do it, for your convenience:

(a)您可以首先创建一个对话(POST/groups//对话).您将指定一个新线程并在请求正文中发布.成功的查询将创建该新对话，话题和帖子.

(a) You can first create a conversation (POST /groups//conversations). You would specify a new thread and post in the request body. A successful query would create that new conversation, thread and post.

(b)或者，您可以创建没有引用任何现有对话的线程(POST/groups//threads).您将指定新线程并在请求正文中发布.成功的查询将创建一个包含该新主题和帖子的新对话.

(b) Or, you can create a thread without referencing any existing conversation (POST /groups//threads). You would specify the new thread and post in the request body. A successful query would create a new conversation containing that new thread and post.

创建帖子后，您可以通过指定父对话和主题或仅指定父主题来使用其ID获取，回复，转发，创建或访问该帖子的附件.这就是所谓的会话和线程奇偶校验.

After a post is created, you can use its ID to get, reply, forward, create or access attachments for that post by specifying both the parent conversation and thread, or just by specifying the parent thread. This is the so-called conversation and thread parity.

• 在这里，我假设同一主题的意思是在该对话的保护下?"

是的，对话，其话题和帖子都共享同一主题.我认为这里的主题"由topic属性表示.

Yes, a conversation, its threads and posts all share the same subject. I think "subject" here is represented by the topic property.

• 如果对话线程是帖子的集合，那与对话所提供的内容几乎相同吗?"

在对话下将话题和帖子放在一起的是主题".在最终用户场景中想一想-对话中的某个人更改了主题后，该人便开始了新的对话. 在对话中，有时，参与者可以与原始参与者的子集分离出一条侧线.这构成了一个新的主题"，因为主题保持不变，参加者减少了. 这就是对话和线程之间的功能设计差异.在API功能方面，您可以回复线程(或帖子)并引用父线程，但不能仅通过引用父会话进行回复.

What pulls threads and posts together under a conversation is the "subject". Think of it in the end user scenario - once a person on a conversation changes the subject, that person starts a new conversation. In a conversation, sometimes a participant can spin off a side thread with a subset of the original participants. That constitutes a new "thread", as the subject has remained the same, just fewer participants. Such is the feature design difference between conversations and threads. In terms of API functionality, you can reply to a thread (or post) and reference the parent thread, but you cannot reply by just referencing the parent conversation.

• 还尝试在新创建的主题中创建新帖子"

我怀疑您对现有线程进行了POST尝试创建帖子?

I suspect you did a POST to an existing thread to try to create a post?

如果是这种情况，我想指出您不能使用POST来创建新的群组帖子.您可以通过以下方式之一创建帖子: -创建新对话时(POST/groups//对话) -创建新线程时(POST/groups//threads) -回复主题时 -回复帖子时

If that's the case, I'd like to point out that you cannot use POST to create a new group post. You can get a post created in one of the following ways: - When creating a new conversation (POST /groups//conversations) - When creating a new thread (POST /groups//threads) - When replying to a thread - When replying to a post

希望有帮助.

Angelgolfer-ms

Angelgolfer-ms

这篇关于会话线程和会话之间有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！