将多个桌面应用程序连接到一个在线数

Question

I'm starting a new project. It consists of:

• Java desktop application downloadable from the internet with a client database.
• PHP website on the internet with a server database.

The user who downloaded the app will use it to add items (not important what are they now) to the local database offline. When/If he is online, the item will be added to the server database so other connected users (through the desktop app or through the website) will see it. I googled the issue and found it's more complected than I guess. One of the solution is to use some ready tools like SymmetricDS and Daffodil to gain in term of security , performance and scalability , but they're difficult to configure and install in both client and server side, and need the access to command prompt which requires me to pass to a dedicated host (well, that is not a real problem). Also, all what I want is just what I've described, not all what these tools actually provide.

• Can I achieve that by myself within my Java application and maybe with the help of the web server PHP?

I'm using MySQL for the info.

Edit: what really matters is to send items to the server database. Reading it can be less tricky using RSS Feed reading, for example.

Answer 1

Basically, you can use HTTP/HTTPS API. When a user online, send items to your php file and mark the items "sended" at local database. But you have to control edited or deleted statuses. So, yes that is much complicated but a solution.

Answer 2

Well the easiest solution that comes to my mind would be to save for each item a last edit date (on the server as well as on the client). Additionaly you have to keep track when a client got his last update from the server.

So whenever a client goes online the server sends him all updates.

But for that you have to make sure that the time on the client and the server are the same, and it doesn't solve the problem what happens if two clients edit the same item.

Answer 3

CouchDB solves the distributed synchronization problem very nicely, but it is a NoSQL DB. Depending on what your application should do, using it would boil down to using instances of CouchDB both locally inside very application, and on the central server.

You'd have to deal with conflicts nevertheless. The only thing CouchDB will support you with is easier detection of conflicts, and the data of both conflicting edits, so your application can work it out either automatically, or with user help.

On the other hand, generatin a unique id on the central server can be as easy as adding the creating user's id to each item id.