More...
The current impl provides factories for lookup of services. I've coded things in a way that would allow us to, for a Phoenix block, forget the factory and switch to an IoC way of specifying the publication context.
ARMI (if we like it) could be used in a few of ways....
1) Applications that have a remote client (say GUI) could...
a) Use ARMI direct. Mount their own server accepting connections on a socket and the
client knows where to look.
b) <depend> on a Phoenix block that provides publication (and possibly lookup) services. This would be similar to the Soapification service/ Glue block. Except that it is not
entirely dynamic.
c) Get publication context from BlockContext. This would imply that it is build in to
Phoenix.
2) Phoenix uses Armi internally to bind blocks to each other that are not in mutually visible nodes of a classloader tree. I would suggest the ObjectStream over Pipe transport for this, though that would require seperate threads (or maybe buffers).
Regards,
- Paul H
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
