On 11/4/10 3:15 AM, Andrea Messina wrote:
Why aren't the following two entries handled in the right way by any
StatusNet account/microblog??
<entry>
*<id>http://example.com/notice/12</id>*
<thr:in-reply-to ref="http://example.com/notice/11";
href="http://example.com/notice/11";></thr:in-reply-to>*
</entry>
<entry>
*<id>http://example.com/notice/11</id>*
> </entry>
[snipped]
i should see the former post, in the same context of the latter, but i
don't......perhaps there is some problem parsing entry feeds that
haven't any ostatus:conversation element inside, when published along
with thr:in-reply-to elements.....
It looks like in our current code, the <ostatus:conversation> info
doesn't actually get used for saving threading info -- just the
<thr:in-reply-to> reference.
I believe it should work correctly, as long as the *latter* message (the
one being referred/replied to) has been received and processed first.
If the referenced replied-to notice "http://example.com/notice/11"; is
present in the system when we process the reply (#12) then it should
indeed mark #12 as a reply to #11, in the same conversation that #11 is in.
However, if when we receive and process #12 we don't have any notice
"http://example.com/notice/11"; in our system, then we don't have
anything to connect it to at that time. The reply-to information will be
dropped and not saved, and it'll be treated as a new message in its own
conversation thread.
If we then receive #11 later, it's too late -- the reference has been
lost and it doesn't get retrofitted into the already-saved #12.
If you're quite sure that #11 is in the system before you're processing
#12, then we'll want to figure out why it's not working...
-- brion
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
