This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Even if you can answer this is general, I don't think it will do you any good. Suppose you have a scenerio such as:
1) call routine to check that remote RMI server is up.
2) if not up, print error message and take a nap for a while, go to 1)
3) prepare to download, make sure there is enough disk space locally to store, etc.
4) start the download
5) save the results
What happens if the remote RMI server goes away, crashes, network failure, etc. between 1) and 4)?
More importantly, why are you thinking of using RMI for this?