Proxy Plugin: Support Forcing Remote FrameX Plugin Invocation via Parameter

[touale]

Background

FrameX supports a multi-plugin architecture. One of the plugins, the Proxy Plugin, enables cross-plugin invocation with the following behavior:

• When a plugin is invoked
• If the plugin does not exist locally
• The proxy plugin automatically forwards the call to the remote FrameX plugin
• This process is completely transparent to the caller

This mechanism works well, but the invocation path is currently determined solely by whether a local plugin exists.

Problem Statement

In practical scenarios, there are cases where:

• A plugin exists locally, but
• The caller still wants to explicitly invoke the remote FrameX plugin

Currently, there is no way to override the default behavior and force a remote invocation when a local plugin is present.

Proposal

Introduce an additional configuration parameter (e.g. from_remote) to the proxy plugin invocation logic.

Expected Behavior

• By default (no parameter specified):
  • Existing behavior remains unchanged
  • Local plugin is preferred if available
• When from_remote = true is specified:
  • The proxy plugin skips the local plugin
  • The invocation is forwarded to the remote FrameX plugin
  • The process remains transparent to the call

Benefits

• Enables explicit control over local vs remote plugin execution
• Supports scenarios such as:
• A/B testing between local and remote plugins
• Debugging and validation of cloud plugins
• Gradual rollout or fallback strategies
• Maintains backward compatibility and transparency