How closer LipeRMI will be from original Java RMI?
I don’t see any advantage to use exactly the same API which Sun uses. This new reimplementation must be a little for ahead and must improve anything is possible, including API. By the way, let’s see an example. Another RMI problem is how to know along the application session which remote clients remains active. And with Java RMI the only way to know this is testing the client; ie. invocating some dummy-ping-test-method and catching exceptions – which costs some precious bandwidth. Now, with LipeRMI API you can use listeners to know at realtime when a new connection was established or closed; saving your bandwidth and making your application more clean and readable.
Related Questions
- Why does my application sometimes receive a NativeSeqFile error when using JRIO and the Remote Method Invocation (RMI) - Java Remote Method Protocol (JRMP) to access MVS datasets?
- Can I Get Java Games, Downloads and Applications on the Original CECT P168 iPhone Clone?
- Why rewrite RMI? What are the original RMI problems?
