Ticket #522 (new enhancement)

Opened 4 years ago

Last modified 12 months ago

Make streaming server attached to one or more client application.

Reported by: robert Owned by:
Priority: major Milestone: MediaMosa 3.1/3.5
Component: Core Version:
Keywords: Cc:
MoSCoW: Must Have Estimated time after impact analysis:
Related to project: none Tested: no
Accepted: no Estimated Hours: 0

Description

See original request at  https://github.com/mediamosa/mediamosa/issues/6

By attaching streaming servers to client application(s), object code returned will then be based on original connecting client application and provide the user specific object code used by the client application. However, we need to see what happens to master-slaved assets/mediafiles (do we use the connecting client or the application of the asset/mediafile).

Change History

Changed 4 years ago by Michiel.Schok

Preferably we use the 'slave' defenitions aka the Connecting Client.

Considering SURFmedia, we would love to use different objectcodes from the general ones.
see ticket #171 , which got postponed from 2.1 to 2.2 to 2.3 via 3.0 to finally x.x

Changed 3 years ago by Frans

  • milestone changed from Community Related Issues to MediaMosa 3.5

Changed 3 years ago by Frans

  • moscow changed from Should Have to Must Have

Changed 12 months ago by Robert

In MediaMosa 3.5.1 we added the option to allow client apps to select a different 'viewer' that will generate a different object_code per selected streaming server.

Note: See TracTickets for help on using tickets.