Terminal / Panel PC - Single Server Solution: Client/Server or RDP?
Posted
by StillLearning
on Stack Overflow
See other posts from Stack Overflow
or by StillLearning
Published on 2010-04-09T01:18:30Z
Indexed on
2010/04/09
1:23 UTC
Read the original article
Hit count: 400
Hi,
Our current setup involves a touch screen panel pc with embedded windows, that is connected via network to a server / dedicated pc, within the same physical location. Each of our 'units' has this hardware setup.
For a quick resolution we deploy our application to the dedicated pc, and have the panel pc remote desktop to an account which then activates the application. This works but seems a little clunky / rough approach. We did this because the panel pc is rather limited.
Now that we have more time, I was wondering if I should separate the application into a gui / application. Deploy the gui logic on the panel pc, and the business/database logic on the dedicated pc.
The app is in Java so I was wondering what technology would be best? I was thinking of using RMI, but its not really a client/server app, as there is only one client. Should I stick with RMI, or use Sockets or something else?
It will be easy to implement as the application is old, and manually wraps and unwraps data which passes through one class / method call to remote services. All I would have to do is 'RMI' this one method call, and the app will do its own stuff.
Cheers.
© Stack Overflow or respective owner