How should I partition classes at the RMI codebase among jar and class files?
The two potentially contradictory goals you should aim for when thinking about how to partition the classes you need to make available through the RMI codebase are minimizing download time for needed classes and minimizing downloading of unneeded classes.If you place only individual class files at the codebase, then clients won’t have to download any class files they don’t require. They will, instead, grab each class file they need individually. This approach eliminates the downloading of unneeded classes, however, it may not yield the minimum possible download time for needed classes.When you place only individual class files at the codebase, clients must make a separate HTTP request for each class file. Were you to place all your class files in a single JAR file, only one HTTP request would be needed to grab the JAR file, which contains all the class files.
Related Questions
- All other necessary classes and jar files are managed by the startserver script or batch file. Where are the classes for JSPs and Servlets?
- Are the zip files this library makes compatible with the Java.util.zip classes in the Java class library?
- How should I partition classes at the RMI codebase among jar and class files?
