Re: [AM] modelling the state of a service

(responding to Ashley, Ian)

> ... There is then the "design" issue of how the value of a
> derived state is refreshed.  Polling as an option but, in
> general, not the only one. Again, exactly the same issue of
> value refresh exists with derived attributes.

The last time I implemented something like this, we opted 
for Polling because a service could fall over without
informing clients that it was about to do so - theoretically.
We considered 'heartbeat' messages as an alternative,
but polling won out because it only happened when the
information was needed.


Paul  Oldfield
www.aptprocess.com

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: [email protected]

TOPICA - Start your own email discussion group. FREE!
http://www.topica.com/partner/tag02/create/index2.html
--^----------------------------------------------------------------