Bug 1548407 - [CodeChange] get rid of SpiceVersion.txt and its handling
Summary: [CodeChange] get rid of SpiceVersion.txt and its handling
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Alexander Wels
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-23 12:34 UTC by Tomas Jelinek
Modified: 2022-02-23 14:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-10 00:56:04 UTC
oVirt Team: UX
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44791 0 None None None 2022-02-23 14:25:06 UTC

Description Tomas Jelinek 2018-02-23 12:34:15 UTC 
Description of problem:
Back in the days when the SPICE client has been opened using ActiveX or XPI plugins, the ActiveX one supported a parameter called "version" which was a way how to update the plugin to the newest version.

Today, for the same thing we use the RemoteViewerSupportedVersions and RemoteViewerNewerVersionUrl from vdc_options.

But, we still ship the SpiceVersion.txt and we still load it on frontend and are parsing the version out of it. It would be nice to get rid of it completely.
Comment 1 Greg Sheremeta 2018-10-10 00:56:04 UTC 
Unfortunately we don't have capacity to work on this.
Note You need to log in before you can comment on or make changes to this bug.