A remote plug-in package must include a primary server that serves the plug-in manifest file. A plug-in can also include auxiliary servers that serve other plug-in resources.

Plug-in packages must be downloaded with secure HTTP (HTTPS) protocol.

You might want to design a plug-in with auxiliary servers for several reasons:

  • To provide load balancing

  • To separate performance tiers

  • To manage security risks

  • To localize database access

  • To take advantage of different coding languages or frameworks

  • To facilitate re-implementation

For more information about auxiliary servers, see Advanced Considerations for Remote Plug-in Servers.