On 03/04/2012 07:53, Andrea Campi wrote:This sounds like the ideal solution. From the replies it sounds like a few people have this issue and have found ways to deal with it, however this would seem like a better implementation as it makes it clearer that this data has been made available by the LWRP and gives a clear indication of when the data will be available. I think node.run_state will do what I want, so I'm going to take a look at it, but I feel that it may not be as clear for other people looking at my code how/when something was pushed into the node.run_state. Andrea's suggested solution feels much more explicit, which I prefer.
We could store a reference to either the Notification or
notification.notifying_resource in the run_context, so that the
notified resource could access it.
I don't see a real downside here, and it.
If there is, as you say, no downside, then providing this as an optional way of approaching the problem leaves the choice down to the developer of the LWRP/resource as to how they wish to implement it.
Either way, I'm very impressed with the amount of constructive responses, what a great community! Your help is much appreciated.
Archive powered by MHonArc 2.6.16.