Server edition support

Flash Media Enterprise Server, Flash Media Interactive Server, and Flash Media Development Server support the following plug-ins:

  • Access plug-in

  • Authorization plug-in

  • File plug-in

Flash Media Streaming Server supports the following plug-in:

  • Access plug-in

About versioning

The Authorization plug-in and the File plug-in have versioning and accompanying create and destroy methods. The Access plug-in does not have versioning. The server detects the plug‑in version number for the File and Authorization plug‑ins based on the value returned by the create and destroy methods. To use the methods of a certain server version, use the correct create or destroy method and return the correct version number. For example, to use Flash Media Server 4.0 features with the Authorization plug-in, call FmsCreateAuthAdaptor3() and return 2.0.

Note:

To limit a plug‑in to Adobe Media Server 3.0 features, return version 0.0 from a call to FmsCreateXXXAdaptor2().

For more information on the versioning APIs, see Adobe Media Server Plug-in API Reference.

The File plug-in has the following versioning:

Server version

Plug-in version

Create and Destroy method

Adobe Media Server 3.0 and earlier

0.0

FmsCreateFileAdaptor()

FmsDestroyFileAdaptor()

Adobe Media Server 3.5

1.0

FmsCreateFileAdaptor2()

FmsDestroyFileAdaptor2()

Adobe Media Server 4.0

1.0

FmsCreateFileAdaptor2()

FmsDestroyFileAdaptor2()

The Authorization plug-in has the following versioning:

Server version

Plug-in version

Create and Destroy method

Adobe Media Server 3.0 and earlier

0.0

FmsCreateAuthAdaptor()

FmsDestroyAuthAdaptor()

Adobe Media Server 3.5

1.0

FmsCreateAuthAdaptor2()

FmsDestroyAuthAdaptor2()

Adobe Media Server 4.0

2.0

FmsCreateAuthAdaptor3()

FmsDestroyAuthAdaptor3()

Upgrading a plug-in

All Flash Media Server 3.5.x plug-ins work on 32-bit Flash Media Server 4. To use new features in Flash Media Server 4, including new APIs, upgrade your plug‑in. If you do not intend to use the new features, you can continue to use your existing plug‑in code.

To use 32-bit plug-ins on a 64-bit system, recompile the plug-ins with a 64-bit Flash Media Server library.

Recompile 32-bit plug-ins for a 32-bit server

  1. Recompile the plug‑in with Microsoft® Visual C++ 2003, Microsoft® Visual C++ 2005, or Microsoft Visual C++ 2008. On Linux, recompile the plug‑in with GNU Compiler Collection 4.x, for example, GCC 4.1 which installs with CentOS.

  2. For the File plug‑in, use the FmsCreateFileAdaptor2() and FmsDestroyFileAdaptor2() methods and return version 1.0.

  3. For the Authorization plug-in, use the FmsCreateAuthAdaptor3() and FmsDestroyAuthAdaptor3() methods and return version 2.0.

Recompile 32-bit plug-ins for a 64-bit server

  • When porting 32-bit plug-in code to 64-bit code, be aware that the data types of some fields have changed.

  • Use the include files and libraries in the rootinstall/samples/plugins/include folder to compile the plug-ins.

  • On Linux, there are two makefiles: MakeFile.AuthModule64 and MakeFile.AuthModule. To compile for 64-bit, use MakeFile.AuthModule64.

  • On Windows, install the 64-bit compiler for Visual C++ in Visual Studio 2008 or later. Choose Build > Configuration Manager and select Release x64. Build the 64-bit installation.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy