Cached json objects were reused when sending notifications to
clients. This created a problem when there were different versions
of monitors coexiting. E.g. clients expecting version2 notification
would receive messages with method == "update2" but payload in
version1 format, which end up failure o
Cached json objects were reused when sending notifications to
clients. This created a problem when there were different versions
of monitors coexiting. E.g. clients expecting version2 notification
would receive messages with method == "update2" but payload in
version1 format, which end up failure o
On Tue, Dec 15, 2015 at 07:06:34PM -0800, Han Zhou wrote:
> Cached json objects were reused when sending notifications to
> clients. This created a problem when there were different versions
> of monitors coexiting. E.g. clients expecting version2 notification
> would receive messages with method =
On Tue, Dec 15, 2015 at 8:24 PM, Ben Pfaff wrote:
> On Tue, Dec 15, 2015 at 07:06:34PM -0800, Han Zhou wrote:
> > Cached json objects were reused when sending notifications to
> > clients. This created a problem when there were different versions
> > of monitors coexiting. E.g. clients expecting
On Tue, Dec 15, 2015 at 7:06 PM, Han Zhou wrote:
> Cached json objects were reused when sending notifications to
> clients. This created a problem when there were different versions
> of monitors coexiting. E.g. clients expecting version2 notification
> would receive messages with method == "upda
Hi Andy,
Thanks for your review.
On Thu, Dec 17, 2015 at 2:00 PM, Andy Zhou wrote:
>
>
> On Tue, Dec 15, 2015 at 7:06 PM, Han Zhou wrote:
>
>> Cached json objects were reused when sending notifications to
>> clients. This created a problem when there were different versions
>> of monitors coex
On Thu, Dec 17, 2015 at 4:33 PM, Han Zhou wrote:
> Hi Andy,
>
> Thanks for your review.
>
>
> On Thu, Dec 17, 2015 at 2:00 PM, Andy Zhou wrote:
>
>>
>>
>> On Tue, Dec 15, 2015 at 7:06 PM, Han Zhou wrote:
>>
>>> Cached json objects were reused when sending notifications to
>>> clients. This crea