So, we have to move some of our model components off of the web server hardware and
on to the business tier servers. You know this won’t be the last time...
Tim Holloway wrote:I think they are being sloppy. RMI stands for Remote Method Interface. The closest to getting access directly to a Model object would be EJB Entity Beans.
RMI is primarily "obsolete" because the original RMI required that both sides of the conversation be done in compatible versions of Java and because it's not firewall-friendly. However, a web-friendly version - RMIOIP which stands for something like RMI Over Internet Protocols addressed some of that.
RMI is still quite useful, since it has about the lowest overhead of any standard Java client/server protocol, but in most cases, something more flexible and/or web-friendly is desired. The first attempt at that was SOAP - which is regrettably verbose and complicated. The second was AJAX, which, when paired with JSON or YAML is fairly low overhead and easy to work with.
The primary use for RMI is when you want high-performance communication between different JVMs on the same local network.
Ekaterina Galkina wrote:
A silly question, but can REST services (http or not) be an alternative here?
Tim Holloway wrote:The second was AJAX, which, when paired with JSON or YAML is fairly low overhead and easy to work with.
Tim Holloway wrote:ReST is simply a web protocol that avoids keeping a Java HttpSession on the webapp server.
Ekaterina Galkina wrote: 3 tiers of persistence.
The top tier is invoked by....
The second persistence....
The bottom persistence tier is simply the ORM model objects themselves.
They weren't very bright, but they were very, very big. Ad contrast:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton