My main concern was if this would impact our spec support or not.
Having some code in place that does not follow the spec, is something
we usually try to avoid right? :)
John's answer clarified that for me though, seems we have the
'alternate/new' json format for now, which possibly might be added to
the spec if it sticks around, and hopefully later also add code that
deals with the way it's currently documented in the spec.
On Jun 25, 2008, at 3:21 AM, Kevin Brown wrote:
I dunno, I usually don't post threads saying I can't figure out how
to do
something unless someone was expecting that I was doing it. Were you
actually waiting on Cassie on this? If so, yeah -- she probably
should have
given you a heads up that there were some issues. I don't see why
you'd wait
on her though if you've got something that works.
