Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

HsinTzu Chen
5,833 PointsDoes send(null) had impact on asynchronous behavior?
I think the synchronous and asynchronous behaviors in first and second example is made by third argument in open method (true: asynchronous or false: synchronous).
However, there is also difference in send method first example (synchronous )-->xhr.send(null)
and second example (synchronous )-->xhr.send()
.
I am wondering if null argument has impact on asynchronous behavior? If not, does anyone knows why null argument is used? Many Thanks!
2 Answers

Steven Parker
220,425 PointsIf you look at the MDN documentation for xhr.send(), you'll find that it says "If no value is specified for the body, a default value of null is used."
So it's simply programmer's preference, either an empty argument or an explicit null
will produce the same behavior.

HsinTzu Chen
5,833 PointsSteven Parker , I see. Next time, I will try to check official document first. Thank you for your explanation!