Ticket #6 (closed task: fixed)

Opened 6 years ago

Last modified 6 years ago

Rework the retrieval of the associated StateVariables when doing an action call

Reported by: dev Assigned to: dev
Priority: major Milestone: first public beta
Component: UPnP Action SubSystem Version:
Keywords: Cc:

Description

Every action call returns one or more StateVariables?. Currently a callback within the action call is used to return the StateVariables? to the calling method.

I think it makes more sense if the returned StateVariables? are propagated through the normal/existing event notification mechanism, meaning the StateVariable? subscription callbacks are automagically triggered when the action call returns successfully.

Things that need to be taken into consideration:

  • actions with only one StateVariable? in return only return the value, not a dict with StateVariable:value pairs
  • the instance the action call is for isn't returned and needs therefore be retained over the call
  • if nothing is subscribed to a StateVariable? change, the result of the action call deflagrates

Change History

03.10.2006 19:32:46 changed by dev

(In [7]) reengineered the way actions are called, breaks Search and Browse actions in ContentDirectory, addresses #6

03.10.2006 23:32:20 changed by dev

(In [11]) some more method calls to test the new action handling, re #6

03.10.2006 23:40:34 changed by dev

(In [12]) added StateVariable? (auto-)update on return of an action call, refs #6

05.10.2006 17:21:21 changed by dev

(In [18]) change re #6

05.10.2006 17:27:44 changed by dev

  • status changed from new to closed.
  • resolution set to fixed.

(In [20]) fix stupid typo and solve browse and search issues, herewith closes #6