I am creating an application where as soon as one user (any of the two) makes changes to his view, the other user sees it (almost instantaneously).
Our server will be handling several "2-user" sessions.
The thing is, that in any given one session (constitutes 2 users), one user can not make any changes to their view unless the other user does their change first.
Would live cycle be mandatory such a case? or could I get away with BlazeDS, so that when a user1 makes changes to his view, updates the server and the server updates user2 which is listening to that session.
Please notify me of any advantages and disadvantages to my reasoning.
