<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
As for this change - changing the name of a returned object's property from "name" to "status" hardly seems like sufficient reason to break backward compatibility. The only thing arguing in it's favor is that it would seem that less that a dozen people worldwide have used the API thus far - so it's probably now or never, at the least.<br>
<br>
If we're going to break backward compatibility, I suspect a more compelling rationale would be required.</blockquote><div><br>Getting back on topic after the entertaining and obviously futile discussion of backwards compatibility, I think in this case the property name "name" on the data object of an Ajax callback is one that few people will understand. Meaning at first look (or a look after a period of rest) they will think, "name of what". I believe strongly that the payload API will be more well received if the property name is "status".<br>
<br>-Dan</div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>