2011-06-09, 11:57
topfs2 Wrote:Forgot to say that we could add \n between notifications if we wanted, afaik its not outside the spec. Anything in between the json objects is meant to be thrown away if we have proper parsers.
I do think its better if we don't have anything in between though, as it makes writing parsers easier IMO (don't have to think about throwing away the wrong data). And checking for \n is not that safe at any rate as you could have \n in a string also (very unlikely though).
Yeah I've gone with some custom code to find the chunks of json that should take into account {} occurring within strings. If anyone is interested it is at 2661473e, which shows the change from basic bracket count chuncking to this new method.