Proposal: rename "asynch-output-input"

I made a misstep in naming one of the added patterns, using the term
"asynch" because I couldn't, at the time, think of a better
distinguisher.

A name that better fits the pattern used throughout part two would be:
"output-optional-input".  That is, output followed by (optional) input. 
This helps distinguish it from the output-input pattern (where input is
required), but does not give the (misleading) impression that it can
only be used in an asynchronous environment (although it *is* true that
using output-optional-input in a synchronous environment is a bear with
cubs).

Amy!
-- 
Amelia A. Lewis
Architect, TIBCO/Extensibility, Inc.
alewis@tibco.com