jQuery in Action, 3rd edition
The moose likes Beginning Java and the fly likes Modular RMI design Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Beginning Java
Bookmark "Modular RMI design" Watch "Modular RMI design" New topic

Modular RMI design

Matt Kim

Joined: Mar 01, 2004
Posts: 26
Hi everyone,
I'm faily new to java and I don't have any formal training in Software Engineering so here's my question to you.
I'm looking into designing a modular application (nothing complex). How extreme would you recommend in modularizing the app? For instance, if I had the following components within an app:
If one class required the other, should they be "passed" into one another i.e.
InventoryManager inventoryManager = new InventoryManager(orderManager);
Or should they be discussing over an RMI connection?
Thanks in advance,
Ernest Friedman-Hill
author and iconoclast

Joined: Jul 08, 2003
Posts: 24199

Welcome to JavaRanch!
Have all the classes in one program. Use RMI only when you have to write two programs and they need to communicate -- for instance, when the two programs have to run on separate machines.

[Jess in Action][AskingGoodQuestions]
I agree. Here's the link: http://aspose.com/file-tools
subject: Modular RMI design
It's not a secret anymore!