I think input/output (I/O) makes sense when you interface with a "closed" system. Meaning there is an inside and an outside, and not much else to care about.
What you describe Phillip is a communication tool, and then it is a different game. Request/Response seems OK. The best thing is to just analyse the system and choose a vocabulary that best describes what the actors do. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=39042 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
