Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
CoffeeScript Application Development

You're reading from   CoffeeScript Application Development What JavaScript user wouldn't want to be able to dramatically reduce application development time? This book will teach you the clean, elegant CoffeeScript language and show you how to build stunning applications.

Arrow left icon
Product type Paperback
Published in Aug 2013
Publisher Packt
ISBN-13 9781782162667
Length 258 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Ian Greenleaf Young Ian Greenleaf Young
Author Profile Icon Ian Greenleaf Young
Ian Greenleaf Young
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

CoffeeScript Application Development
Credits
About the Author
Acknowledgements
About the Reviewers
www.PacktPub.com
Preface
1. Running a CoffeeScript Program FREE CHAPTER 2. Writing Your First Lines of CoffeeScript 3. Building a Simple Application 4. Improving Our Application 5. Classes in CoffeeScript 6. Refactoring with Classes 7. Advanced CoffeeScript Usage 8. Going Asynchronous 9. Debugging 10. Using CoffeeScript in More Places 11. CoffeeScript on the Server Index

Understanding asynchronous operations


It's a word you've probably heard before, but may not understand exactly what it means or why we care. Asynchronous operations are operations that do not block while completing. What does that mean, exactly? Well, synchronous operations (the vast majority of commands in a program) get executed one at a time, in order. Consider this code:

mixBatter()
bakeCake()
frostCake()

Each of these functions is invoked in order, and not until the previous function returns. bakeCake is only invoked after mixBatter returns, and frostCake is invoked only after bakeCake returns. If bakeCake takes 40 minutes to return, well, frostCake will have to wait 40 minutes before it can run. We could say that bakeCake blocks execution until it is finished.

This makes the code very easy to reason about, and most of the time it's the behavior that we want. However, there are times where we might wish to start an operation but not wait for it to finish before doing more work. Most often...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image