etch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "scott comer (JIRA)" <>
Subject [jira] Created: (ETCH-7) @AsyncReceiver is too coarse a mechanism
Date Mon, 17 Nov 2008 13:59:44 GMT
@AsyncReceiver is too coarse a mechanism

                 Key: ETCH-7
             Project: Etch
          Issue Type: Improvement
          Components: compiler
    Affects Versions: 1.0.1, 1.0.0
            Reporter: scott comer
            Priority: Minor

@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

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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message