Difference: ApplicationsMessagingInitialQuestionsFive (1 vs. 3)
Revision 32012-06-26 - root
Application discoveryHow should applications discover each other? Dynamically at runtime? Statically through some registry mechanism? Can we start apps that aren't running or is this beyond the scope of the messaging group?_Dynamic discovery is possible, and static discovery via description of application capabilites in the registry would be useful - although is this in the scope of a messaging spec? Starting applications that aren't running at the moment is hard to do (for all platforms, for all kinds of application). It's unclear whether this needs to be integrated into the spec any more than defining something like a, eg, 'launchDefaultTableViewer' message (or maybe a more general launch message which was paramterized on some kind of capability, or type of message to consume) . Then if a 'launcher' application is available that can accept these messages, it'd be discovered dynamically. (often, it'd make sense to bundle the 'launcher' app with the hub itself) However, just being able to query the registry to suggest applications to the user would be a start -- NoelWinstanley_ |
Revision 22007-02-08 - NoelWinstanley
| ||||||||
| Deleted: | ||||||||
| < < | ||||||||
<--
Application discoveryHow should applications discover each other? Dynamically at runtime? Statically through some registry mechanism? Can we start apps that aren't running or is this beyond the scope of the messaging group? | ||||||||
| Added: | ||||||||
| > > | _Dynamic discovery is possible, and static discovery via description of application capabilites in the registry would be useful - although is this in the scope of a messaging spec? Starting applications that aren't running at the moment is hard to do (for all platforms, for all kinds of application). It's unclear whether this needs to be integrated into the spec any more than defining something like a, eg, 'launchDefaultTableViewer' message (or maybe a more general launch message which was paramterized on some kind of capability, or type of message to consume) . Then if a 'launcher' application is available that can accept these messages, it'd be discovered dynamically. (often, it'd make sense to bundle the 'launcher' app with the hub itself) However, just being able to query the registry to suggest applications to the user would be a start -- NoelWinstanley_ | |||||||
Revision 12007-02-08 - JohnTaylor
<--
Application discoveryHow should applications discover each other? Dynamically at runtime? Statically through some registry mechanism? Can we start apps that aren't running or is this beyond the scope of the messaging group? |
View topic | History: r3 < r2 < r1 | More topic actions...
Copyright © 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