bucketsStreaming seems to have everything in it, including uptime, memory usage, and other fields that change, even if the configuration does not change.

bucketsStreamingConfig was meant to be more 'stable', in that if the configuration is the same, a simple strcmp() shows equality.

If no one objects, we should just collapse these and have just bucketsStreaming (turn that into the same as what bucketsStreamingConfig provides today). If the client wants to see uptime or other details, they can use 'buckets'.

Steve
________________________________________
From: Aliaksey Kandratsenka [alkondratenko@gmail.com]
Sent: Friday, July 30, 2010 6:03 PM
To: Steve Yen
Cc: Matt Ingenthron; Perry Krug
Subject: Re: Fwd: Forum help

On Fri, Jul 30, 2010 at 5:08 PM, Steve Yen <steve.yen@northscale.com<steve.yen@northscale.com>> wrote:
Thanks Matt.

Also cc'ing Alk, as he's been in that code the most recently and might know offhand. The quick summary was that Atilla (the enyim C# client author) was seeing...

pools/default/bucketsStreaming/default

...disconnect after the first JSON msg instead of streaming.

Yeah. Seen that, but haven't got to seeing why. BTW, we also have bucketsStreamingConfig. And that streams correctly. What's the difference ?