ActiveX SDK
For ISVs with access to their application's source code, WebStream offers an ActiveX integration layer that enables richer, in-application capabilities beyond what publishing as-is provides.
When to use deep integration
Most ISVs start by publishing their application as-is. Consider the ActiveX layer when you want your application to participate directly in browser-side capabilities — for example, tighter control over file exchange, browser-native interactions, or edge features — and you are able to make targeted changes to your code.
What it enables
- Programmatic interaction with WebStream's file and browser bridge from within your application.
- Richer integration of edge features into your product's own workflows.
- A path to differentiate your browser-delivered product beyond the standard streaming experience.
Getting the SDK
The open-source ActiveX control, API samples, and issues are on the WebStream GitHub repository. See the API Reference for links and entry points.
Deep integration is optional. You can ship a fully browser-delivered, governed product with no code changes by publishing as-is — see Publishing Your App.