Hey all, I was asked about RMI today, and whether the ME project should pursue a kRMI solution on top of MIDp. There are already open source implementations out there that we could talk to about joining our project, but I'm not certain that we want to invest here. Off the top of my head, these were my early thoughts: REASONS NOT TO IMPLEMENT RMI on MIDp - RMI implementations will likely be large if they are useful, and MIDp RAM is too small already - RMI exists in Pjava, so for the larger devices [WinCE, Palm, etc.], there is a solution already - RMI exists in some third party KVMs already [kada, esmertec, etc.] - RMI may exist in PDAp (Stefan, can you confirm/deny this without getting in trouble?) - kSOAP gives us some of the benefits of RMI, but none of the Java-only limitations REASONS TO IMPLEMENT RMI - RMI is the first thing every developer howls about as 'missing' on J2ME/MIDp - It's easier to load a class than to replace a KVM on these devices - We might be able to do the 80/20 rule and get 80% of the functionality for 20% of the coding Comments? thanks, kb |