How do we balance the need for messages to be general enough for max interop, with the specificity needed to exploit the full power of an app?

Example 1. We might define a message that can load an image, but some applications are capable of loading several images at once.

Messages might mean different things to different apps.

E.g. a 'loadImage' message might mean to render it for display to one app, plot its histogram to another, or stage it for processing to third. How do we deal with this in a user-friendly way?
Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2007-02-08 - JohnTaylor
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback