CLI Adapter for Legacy Command Syntax Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing command line interface (CLI) commands in client-server networks is inefficient due to the need for separate plugins to support legacy and updated syntax, requiring duplicated functionality and increased development effort.

Innovation Solution

A CLI provider with an adapter converts legacy CLI command information into updated CLI command information, which is then submitted to a plugin for processing, utilizing the Windows registry to determine and perform syntax conversion, thus eliminating the need for separate plugins.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate plugins are used to support legacy and updated CLI syntax, then both legacy and updated command support is provided, but development effort and system complexity increase due to duplicated functionality

Engineering Contradiction:
ImproveCLI syntax compatibilityVSAvoidplugin architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A syntax adapter is introduced as an intermediary component between the CLI provider and plugins. The adapter receives legacy CLI commands, converts them to updated syntax, and forwards them to plugins. This mediator eliminates the need for separate legacy and updated plugins, reducing system complexity while maintaining compatibility with both legacy and updated CLI syntax.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If separate plugins are used for legacy and updated CLI syntax, then full command support is maintained, but development effort increases due to duplicated functionality

Engineering Contradiction:
Improvecommand support coverageVSAvoiddevelopment effort
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The syntax adapter is designed as a universal component that handles the conversion of legacy CLI commands to updated syntax. By centralizing the conversion logic in the adapter, the same plugin can serve both legacy and updated command requirements, eliminating duplicated functionality and reducing development effort while maintaining full command support coverage.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Device complexity

If legacy CLI commands are converted to updated syntax, then a single plugin can be used, but conversion logic must be implemented

Engineering Contradiction:
Improveplugin quantityVSAvoidconversion implementation
Core Design Contradiction:
Device complexityVSEase of manufacture

Solution Approach 1:

The system is segmented into distinct functional components: the CLI provider, the syntax adapter, and the plugin. The conversion logic is isolated in the syntax adapter segment, which is responsible solely for translating legacy commands to updated syntax. This segmentation makes the conversion implementation manageable and modular, reducing the overall complexity of the system architecture.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8838858B1Managing command line interface commands
Publication Date: 2014.09.16 EMC IP HLDG CO LLC
  • US8838858B1 patent drawing
  • US8838858B1 patent drawing
  • US8838858B1 patent drawing

AI summary

A method is used in managing command line interface commands. Legacy CLI command information is received at a command line interface (CLI) provider. At the CLI provider, it is determined to convert the legacy CLI command information. The CLI provider has an adapter for performing the conversion. Updated CLI command information is derived by the adapter from the legacy CLI command information. The updated CLI command information is submitted to a plugin for processing.