IMO all states should give details where possible. If a machine is sending or receiving I want to see % complete. If it's starting I want to see where we're at compared to the average. In any case giving the user good feedback should be helped rather than hindered. Sam on iPhone On 4/24/09, Randy Bias <randyb@gogrid.com> wrote:
Sorry. That wasn't clear in your initial email on this. I think that's a great idea.
--Randy
On 4/23/09 4:41 PM, "Michael Richardson" <mcr@sandelman.ca> wrote:
> "Chris" == Chris Webb <chris.webb@elastichosts.com> writes: Chris> Randy Bias <randyb@gogrid.com> writes:
I would personally shy away from trying to specify multiple error states. My past experience is that this is an endless bucket. Systems fail in lots of ways. Once you start specifying error states you won't stop.
It's not about multiple error states. It's about having an error state that optionally includes details.
-- Randy Bias, VP Technology Strategy, GoGrid randyb@gogrid.com, (415) 939-8507 [mobile] BLOG: http://neotactics.com/blog, TWITTER: twitter.com/randybias
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg