<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body> <br>nemesis <nemesis@ninux.org> ha scritto:<br>In the refactoring branch, at the moment the available status for <br> devices are:<br><br> * archived<br> * unplugged<br> * not_reachable<br> * reachable<br><br> not reachable and reachable are self explanatory.<br><br> not sure about unplugged.<br><br> In another application I work on in my daily job, there is the <br> "unknown" status, which means the system has never reached the device <br> yet, so the system does not know the device. Which makes sense.<br><br> Unplugged is not a type of status that can be automatically determined.<br><br> Archived means that a device is no longer active, but is mantained in <br> the database for some reason.<br><br> Archived and unplugged are similar, because the user would have to set <br> this status manually and the system should avoid trying to contact a <br> device which is archived or unplugged. So I think we should merge <br> archived and unplugged, but find a better name, plus introduce the <br> "unknown" status, which would be the default.<br><br> This is my new proposal:<br><br> * unknown: device has not been seen by the system yet<br> * not_reachable: device has been seen in the past but is not reachable <br> now<br> * reachable: device is reachable<br> * deactivated / unplugged: device has been deactivated manually by the <br> user<div><br></div><div>+1 </div><div>it's ok<br><br><br> Have your say<br>_______________________________________________<br>Nodeshot mailing list<br>Nodeshot@ml.ninux.org<br>http://ml.ninux.org/mailman/listinfo/nodeshot<br></div></body>