Hi Jeremy / Jim, Thanks for continuing to guide me on this :-)
- Jim, the concern you raised about the business interface not inheriting from Remote and the need to do some sort of mediation has been a primary concern to me since M1. I have been able to get that working now. Now there is no requirement that interfaces inherit from Remote. - With respect to the system component implementation of RMI Host, I might need help in implementing this. Right now I understand the following: - - that an RMIHost will cache RMI Registries (like the LoaderRegistry caches the Loaders) - each registry is identified by a port on which it runs. I am not sure how hostname can be used for services. However, for references host names has a role to play. Right? - RMI Host will be the interface thro which RMIBinding will register services into one of the registries (based on the port number specified) Can you please point me to some code that I can emulate to implement RMI Host in terms of how it should be implemented as a system component that can be autowired into the builder. Right now I am looking at LoaderRegistry to understand the programming model for this. Am I on track? Thanks - Venkat On 8/12/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On Aug 11, 2006, at 6:29 PM, Jim Marino wrote: >>> Forgot about the host. If we want to have one component per >>> registry, what happens when two services register at the same >>> host/port combination? >> >> If two registries register, the second should fail (as it won't be >> able to get the socket anyway). >> > Right so that's why I was thinking it would be better to allow for > multiple components per registry. Do you think that's not something > that really is a problem? > An RMI registry can support multiple services, see next statement. >> Services will have a uri whose path will distinguish them. RMI services have a URI path that they use to register with the registry so that it can contain multiple ones - like a servlet context is used to allow multiple webapps on the same socket. RHIHost = Web container (ServletHost) RMIRegistry = HTTP listener Remote Service = Servlet RMIRegistry instances are components deployed to the system that listen on sockets and dispatch requests to registered services based on URI path. -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
