http://defect.opensolaris.org/bz/show_bug.cgi?id=12885
Summary: state changes in nwamd should be immediate
Classification: Development
Product: nwam
Version: RC6
Platform: ANY/Generic
OS/Version: All
Status: ACCEPTED
Severity: enhancement
Priority: P2
Component: ON daemon
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: alan.maguire at sun.com
QAContact: nwam-dev at opensolaris.org
--- Comment #0 from amaguire <alan.maguire at sun.com> 2009-11-25 15:06:56 UTC
---
currently in nwamd, when we call nwamd_object_set_state(), this merely creates
and enqueues a state change event. Problem is, when we do this, other (possibly
contradictory) events could be enqueued ready to be processed, after which the
state change will no longer make sense. It might make sense to process state
changes immediately. However, some investigation needs to be done on the 73
invocations of nwamd_object_set_state(). Firstly, we need to determine how many
call the function with the object lock held, and in what context (worker thread
versus main event-processing thread). We also need to consider how making state
events immediate may work in the light of event chains that consist of requests
which lead to state changes (which in turn may lead to other state changes).
None of this will likely preclude the immediacy approach, but we need to tread
carefully.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
