GitHub user dlaboss opened a pull request:

    https://github.com/apache/incubator-quarks/pull/116

    [WIP] [QUARKS-22] [COMMENTS?] StreamScope

    Open for comments on "API", behavior and impl (where not marked as TODO).
    The DevelopmentProvider adds StreamScope peekers.
    StreamScope's will be registered with a new StreamScopeRegistry runtime 
service.
    The Console will lookup a stream's StreamScope (to enable&configure) via 
the StreamScopeRegistry by its associated stream's alias or stream id.
    Still working out the details of StreamScopes getting registered to make 
lookupBy streamAlias or id possible.
    
    - Add PlumbingStreams.StreamScope (Consumer<T>)
    - Add PlumbingStreams.StreamScopeRegistry
    - Add quarks.topology.plumbing.StreamScope oplet (just so console can
    present it differently - remove?)
    - Update DevelopmentProvider to add StreamScopes
    - Add StreamScope and StreamScopeRegistry tests

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dlaboss/incubator-quarks streamScope

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-quarks/pull/116.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #116
    
----
commit 963caa6dccf791a1098a648b683c5934054c6882
Author: Dale LaBossiere <[email protected]>
Date:   2016-05-11T19:53:25Z

    [WIP] [QUARKS-22] Initial StreamScope implementation
    
    - Add PlumbingStreams.StreamScope (Consumer<T>)
    - Add PlumbingStreams.StreamScopeRegistry
    - Add quarks.topology.plumbing.StreamScope oplet (just so console can
    present it differently - remove?)
    - Update DevelopmentProvider to add StreamScopes
    - Add StreamScope and StreamScopeRegistry tests

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to