On Thu, Sep 6, 2012 at 7:49 AM, Ben Pfaff wrote:
> On Wed, Sep 05, 2012 at 11:48:26PM -0700, Ansis Atteka wrote:
>> On Wed, Aug 8, 2012 at 4:14 PM, Ben Pfaff wrote:
>> > Until now, the jsonrpc module has used messages received from the
>> > remote peer as the sole means to determine that the JSON
On Wed, Sep 05, 2012 at 11:48:26PM -0700, Ansis Atteka wrote:
> On Wed, Aug 8, 2012 at 4:14 PM, Ben Pfaff wrote:
> > Until now, the jsonrpc module has used messages received from the
> > remote peer as the sole means to determine that the JSON-RPC
> > connection is up. This could in theory intera
On Wed, Aug 8, 2012 at 4:14 PM, Ben Pfaff wrote:
> Until now, the jsonrpc module has used messages received from the
> remote peer as the sole means to determine that the JSON-RPC
> connection is up. This could in theory interact badly with a
> remote peer that stops reading and processing messag
Until now, the jsonrpc module has used messages received from the
remote peer as the sole means to determine that the JSON-RPC
connection is up. This could in theory interact badly with a
remote peer that stops reading and processing messages from the
receive queue when there is a backlog in the s
