File Handler Integration for Non-Native Web Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face limitations in interacting with and performing custom actions on non-native file types within web-based services, as there are limited ways to preview and interact with the diverse range of files exchanged online.
Innovation Solution
A file handler application is registered with a directory service to integrate non-native files into the web application environment, enabling them to be handled similarly to native files, with a file handler manifest declaring properties and resources for previewing, opening, creating, and saving, and allowing multiple file handlers to manage various extensions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web applications support only native file types, then security and system stability are maintained, but user interaction capability and file handling versatility are limited
Solution Approach 1:
The patent introduces file handler applications as intermediary components that bridge non-native file types and the web application environment. These file handlers are registered with the directory service and act as mediators to enable preview, open, create, print, and save operations for non-native files without requiring changes to the core web application security architecture.
Solution Approach 2:
The patent creates a universal file handling mechanism where a single web application environment can handle multiple file types through registered file handlers. The directory service maintains a universal registry that maps various file extensions to appropriate handlers, allowing the system to provide consistent file operations across diverse file formats without requiring separate applications for each file type.
2Adaptability or versatility
If multiple separate applications are used to handle different file types, then file interaction capability is improved, but data storage and network usage increase
Solution Approach 1:
The patent merges multiple file handling capabilities into a single integrated web application environment. Instead of requiring separate applications for different file types, the system combines multiple file handlers within one web application context, sharing common infrastructure including security protocols, user authentication, and file storage mechanisms.
Solution Approach 2:
The web application environment provides universal file handling capabilities through the directory service registry, which consolidates information about multiple file handlers in one location. This universal approach eliminates the need for separate application installations and reduces overall data storage requirements by sharing common resources across different file type handlers.
3Adaptability or versatility
If file handlers are registered with directory service, then non-native file integration is achieved, but system configuration complexity increases
Solution Approach 1:
The patent implements self-service mechanisms where file handler applications automatically register themselves with the directory service upon installation. The registration process includes automatically declaring file handler manifest properties and associating file handler resources with the directory service, reducing manual configuration requirements.
Solution Approach 2:
The patent employs preliminary action by requiring file handler manifests to be declared in advance with all necessary properties and resources specified before actual file handling operations begin. This preliminary configuration approach allows the system to pre-validate and pre-register file handlers, simplifying the integration process when non-native files are encountered.
Data Source
AI summary
Applications may be created and registered to an online ecosystem and then execute within individual web applications such as productivity applications, communication applications, collaboration applications, and so on. These non-native applications may be enabled to interact with files and provide custom experiences for a user. The applications may also be enabled to interact with additional information discovered about the user within the ecosystem to provide custom experiences. The applications may further be enabled to create custom workflows to allow users to accomplish new tasks.