[
https://issues.apache.org/jira/browse/THRIFT-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734968#comment-16734968
]
Jens Geyer commented on THRIFT-4639:
------------------------------------
Agree with Randy To the point.
[~phlundblom]: I never questoined the tickets contents. But something that lies
around for months where nobody seems to have an serious issue with (potherwise
it would have been tackled much quicker) is not a blocker for the project. It
may be a blocker for you, though, but that's not the question here. If it were,
we would have to mark next to everything as blocker, because everything is
blocking something for someone. So let's stay cool.
> Sequence numbering for multiplexed protocol broken
> --------------------------------------------------
>
> Key: THRIFT-4639
> URL: https://issues.apache.org/jira/browse/THRIFT-4639
> Project: Thrift
> Issue Type: Bug
> Components: Node.js - Library
> Affects Versions: 0.11.0, 0.12.0
> Reporter: PH Lundblom
> Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Handling of client sequence numbering for multiplexed protocol is broken.
> Current implementation uses client internal variable "seqid" which should be
> "_seqid"
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
