Win a copy of TensorFlow 2.0 in Action this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

Need help breaking down this comparison of Intents and API Calls

Ranch Hand
Posts: 50
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi! I just read this excerpt from a blogger in the link below and I'm trying to make sense out of it.

Intents are messages that are passed between components. So, is it equivalent to parameters passed to API calls? Yes, it is close to that. However, the fundamental differences between API calls and intents' way of invoking components is
1. API calls are synchronous while intent-based invocation is asynchronous (mostly)
2. API calls are bound at compile time while intent-based calls are run-time bound (mostly)

From what I can tell, the API calls are calls directly from the Java classes itself.
1. The CPU needs to focus all its attention on API calls. I know Synchronization is necessary in games to prevent coordinate variables from getting mixed up with other variables. Is this the same concept?
2. I never fully understood compiling and run-time. From what I can tell, the API calls while its being built up and Intent calls are fired while the program is executing.

Please tell me if any of that or all of that is wrong.

Thank you.
Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic