Kind of, but not quite.  It really doesn't lock or stop the process, so this function returns immediately.  If you were to call `loadKML` with a KML that has external styles, and step through the debugger, you would see loadKML return before the KML was ever loaded (before the function passed to `when.all` gets called.  So from inside loadKML, it definitely looks like kind of a lock, but the calling code doesn't lock at all and needs to know it's dealing with an asynchronous operation.  You can see this yourself by looking at the `external styles` spec I added.  It has to use the Jasmine (our unit test framework) `waitsFor` command.  If you get rit of the waitsfor and the `runs` and just execute them directly after loadKML, the test will fail.