On Nov 9, 7:29 am, John Resig <jere...@gmail.com> wrote: > As I mentioned before - the application would just break in a > different way. Normally it would break in that the result would never > come in - now it would throw an exception (again, that's assuming that
I dont think thats true. There are plenty of use cases where not getting a result is not a problem - and using $.get in any other situation would be wrong. eg a status box that updates every minute. If the result doesnt come back, you dont update the status. Nobody minds, the status is just a little old. But getting a null result would (or certainly could) break it. So I think your statement only applies to incorrect usage of $.get. Mark -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
