[snip]
Simon Laws wrote:
If we're talking about a domain URI, this is typically model information
that can be hosted in a Top level Composite or Domain Composite or
Domain model object, whatever we want to call it. If I understand the
spec correctly, the cardinality is: 1 Domain -> 1 base URI per protocol
used in the domain. The ExtensionPointRegistry is associated with a
Runtime instance, not tied to a Domain. I'll propose a new model object
to host that domain-wide configuration.
Sounds good to me.
I'm assuming when you say runtime instance here you mean something like,
ReallySmallRuntime. Can you say if you have in your mind some specific
scenarios that leverage the difference between the domain model and runtime
as they exist in the code at the moment, for example, by starting more than
one runtime for a domain model. I'm happy if the answer is "not at the
moment" and that it is just good architecture practice to separate these
clearly distinct parts of the solution.
One example: an administrator creates / edits / updates domain
configuration, without having started any runtime at all :)
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
