On Friday 12 April 2002 02:06 am, Paul Hammant wrote: > The OpenConnection (hidden from you) establishes 'session' . If X is > bought back on lookup and given a refId (hidden again) of 123, andy > other lookup on it is just going to give the same instance and refId.
good to know. I'm slowly digesting the altrmi internals to figure out all the magic. > Harmless. Having said that, I would split my app into two ... a > container concept that knows of AltRMI and does the lookup, and a comp > tha uses it, and has no handle on the interface that can be used for > lookup. I think you have moved beyong the cornerstone transport > packaged yes? I'm using the cornerstone blocks on the server side for publishing, but yes I moved beyond the cornerstone pieces for the client (which is good, since I don't really need the phoenix-client.jar there either). I thought about splitting the altrmi bits into two components, but I would end up with a component that handles the altrmi and another component that returns my work interface. But I've seen posts that having components that are intrinsicly linked like that is bad component design, so each consumer of the altrmi interface gets a handle to the component that can return an AltrmiInterfaceLookup and passes that to a static method in a helper class to return the work interface. Works well enough for the time being, there will be chances to refactor in the future :) -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
