[2005-03-02 22:20] Phillip Rhodes said:
| 3. If you can't get direct access from machine C to machine A, you
| could possibly enable IP forwarding on machine B in some fashion, such
| that you forward the necessary packets between A and C. This might
| depend on machine's A and C being in different subnets however.
I looked for an iptables RMI NATting module, but nothing surfaced.
| 4. I'm not familiar with any product that is specifically an "RMI Proxy"
| but you could probably write your own (application specific) one in
| short order, with a java program on machine B proxying the remote calls
| around. But, performance would probably suck because you'd have two
| remote calls for every method invocation from machine A. That might
| or might not be an issue to you.
After shaking google for a while, rmiproxy.com fell out. The
problem with it is that it requires modification of both sides of
the RMI to work.
Maybe this isn't workable? I sure wish I had a few days to put
into digging deeper into RMI, as my knowledge of RMI is fairly
limited as well. It just seems like someone else would have
hit this problem and solved it in a transparent manner. Surely
I can't be the only person to want this, which makes me think it
might not be possible/feasible... :-\
Into the mire!
Thanks.
Brent
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
