View Single Post
Old March 17th, 2011   #3
nomis52
Task Group Member
 
Join Date: May 2010
Location: San Franciscio
Posts: 57
Default

Responding with an ACK where too much data is provided (like the example you provided) will result in a warning but not a test failure. Responding to a PID that requires data with an ACK generates a test failure.

The reasoning is this: while many would argue that responders should be liberal in what the accept, this can be taken too far. The problems that we face today with browser standards are an example of this, if the early browsers had been much stricter in parsing html we wouldn't be in the mess that we're in.

By being strict, responders can expose bugs in controllers that would otherwise go unnoticed. It's particularly bad in that if you have a liberal responder & buggy controller, introducing a strict controller into the rig will cause people to blame the wrong device.

If RDM were further along I'd have a different opinion but given how early we are in adoption, I want to try and enforce strictness now. Ideally a device would have a custom PID ENABLE_STRICT_MODE (default:True) which would control the level of strictness.

Anyway, that's enough from me. We do have the first responder that passes all tests now - a Creative Lighting Slammo dimmer : http://creativelighting.com.au/index...d=13&Itemid=31
nomis52 is offline   Reply With Quote