- From: Dave Raggett <dsr@w3.org>
- Date: Tue, 2 Jun 2015 19:10:35 +0100
- To: David Janes <davidjanes@davidjanes.com>
- Cc: public-web-of-things@w3.org
Received on Tuesday, 2 June 2015 18:10:40 UTC
> On 2 Jun 2015, at 18:44, David Janes <davidjanes@davidjanes.com> wrote: > > These distinctions become much more obvious when you work with real devices. We, as programmers are using to things happening immediately - we update a database, and the value is what we updated it to. > > This isn't true for Things. This is why developers need to assume an asynchronous approach. In a distributed system this is essential. Could you please provide a use case where you need to know when a property update has taken effect? Perhaps this could be better modelled using an action with a result? That would enable a script to determine when the action had been completed. p.s. in the Web of Things Framework actions may provide asynchronous results. — Dave Raggett <dsr@w3.org <mailto:dsr@w3.org>>
Received on Tuesday, 2 June 2015 18:10:40 UTC