Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: etch-dev@incubator.apache.org
Message-ID: <109572129.1235063283486.JavaMail.jira@brutus>
Date: Thu, 19 Feb 2009 09:08:03 -0800 (PST)
From: "scott comer (JIRA)" <jira@apache.org>
To: etch-dev@incubator.apache.org
Subject: [jira] Created: (ETCH-61) dynamic mixin
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

dynamic mixin
-------------

                 Key: ETCH-61
                 URL: https://issues.apache.org/jira/browse/ETCH-61
             Project: Etch
          Issue Type: Improvement
          Components: csharp-binding, java-binding
            Reporter: scott comer


there are times when a statically constructed mixin isn't quite enough. if you consider an etch gateway or router, then the decision of which etch services need to be accessed on a given connection needs to be made after the connection is established. another form of this is filters which are added at runtime (yes, right now before the connection is established, but perhaps not in the future).

an example of this is a generic gateway between soap and etch. the gateway has a repertoire of say a dozen or more etch services, but it doesn't know which one you want until you actually connect and tell it. so initially you have a simple etch interface you're using, login, etc. then you send a request for some service. the gateway realizes it doesn't yet have that service in your mix, finds it, determines that you can access it and makes the connection, then dynamically mixes it in.

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