[ETCH-7] @AsyncReceiver is too coarse a mechanism

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.0.0, 1.0.1
• Component/s: compiler
• Assignee: Unassigned
• Reporter: Robert Scott Comer
• Created: 17/Nov/08 13:57
• Updated: 17/Nov/08 13:57

Description

@AsyncReceiver allows the specification of the runtime qualities of a message implementation, in particular that the message should not block the message receiver thread but should run asynchronously. there are only two ways to run asynchronously, queued to a thread pool or by running on a free thread.

1) it seems that this is more of a service implementation issue and not a service description issue.

2) the resources allocated to a particular message (pool thread or free thread) are managed at a pretty coarse level. something more fine grained seems to be called for, such as a queue name (to select one of many queues), priority (some messages are more important than others), etc. this might factor into some service description elements but also some implementation tags as well.