Which API should you choose?

• C and C++ programmers should choose the Diva API
• Visual Basic programmers will almost always choose the Diva Component API
• Visual C# programmers can choose between the Diva API for .Net and the Component API.
  • For many C# programmers the Component API is the easiest and most appropriate choice because it includes almost all of the functionality of the C/C++ Diva API while encapsulating and hiding most of the complexity within the Component API objects.
  • C# programmers should choose the Diva API for .Net if they are more comfortable with the C++ style of API than the Component or object model or if they are implementing an application that requires functions currently unsupported by the Component API.

Mixing the APIs - using both Diva API for C/C++ and Diva Component API in one application
The SimplePhone sample shows how a Component API program can use an Audio Provider DLL written in C using the Diva API for C/C++. The Component API program can handle the high-level functions and the GUI while the Audio Provider handles the time-critical streaming functions.