Java Swing client server synchronization and not reinventing the wheel to keep consistency -


i need implement proof of concept application swing application there's server having list of users , several clients connect server , crud operations on database , hence on list of users.

client application example

i have obvious synchronization dilemma of keeping clients lists updated if 1 client removed user 1 still has in list cannot change name. know protocol in before updating user client asks server whether still exists work.

however simple example in real application might have junction tables , complex references between objects need kept consistent , don't want reinvent wheel.

what i'm wondering if there's ready made solutions or library job doesn't require me change database or load extremely complex dependencies.

i did research on google nothing seems fit , similar example of client server synchronization found "chat programs", chat programs inherently simple because message never modified or deleted , have keep consistent chronological order. need more involved or useful hints on subject.

what need sort of messaging between server , clients. clients either long-poll server, asking updates, or subscribe streaming endpoint on server.

you can take on comet model, long-polling itself, websockets, etc.

alternatively - there couple of data management servies - blazeds, graniteds or similar purpose solution. can integrate 1 of in application , use complete data management cycle.


Comments

Popular posts from this blog

node.js - Bad Request - node js ajax post -

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -