Suggestions needed for communication between Java swing based rich clients and Spring-based application server
Posted on 2011-03-16
I am planing a redesign of a (Delphi) client-server application to java ee 6. I would like to use Spring 3 / Hibernate as a middle tier. The middle tier should serve several types of clients, mainly rich desktop clients, but also mobile devices and keeping the possibility to add browser-clients later based on a single middle tier code base.
I am planning to use Swing-based Desktop clients.
What communication type would you suggest for rich desktop clients? RMI?
Is it wise to consider the desktop client as "just another type of client" that communicates with the middle tier like any other client.
This looks clean and nice on an architecture blueprint, but is it practical? Or should I use some more sophisticated construction especially for rich desktop applications? For example to keep up a nice performance?
I read that the best remoting strategy is "not to use distributed objects at all" (Martin Fowler)...
What are your experiences? Suggestions?
Many questions, hope my problem is clear for you.
Thanks a lot, Daniel