Which comma do you parse is the problem -- and then you are writing a JSON parser. I've used newlines in the past to separate JSON objects and think Ken's approach makes sense. A new content type would allow a generic parser to know the right thing to do.
To answer your original question, I have not seen anyone specing this out before. Write something up and post it. -- Dick On Wed, May 23, 2012 at 3:00 PM, Mark Hahn <m...@hahnca.com> wrote: > > it seems that the work on the client side to do streaming parsing > gets much harder > > I don't understand? Parsing commas is hard? However you planned on > parsing newlines could parse commas instead. > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- -- Dick -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
