On 12/04/2010, at 8:22, Jon Seymour <jon.seymour@xxxxxxxxx> wrote:
So, would it be worth providing a hint as to record type in the output_start_object call so that if it was later desired to subsume line-oriented formats under the same framework, there is enough information available to the backend to do that?
Of course, one way to do this would be to use a more descriptive record name than "entry". This would make the record itself (as opposed to just it's fields) self-describing.
The point is, you would want to start using descriptive record names now so that you don't end up locked into a partially context sensitive base of consumers who are expecting their JSON records to be called "entry" and using context hints to infer the actual record type.
jon. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html