Front End Developers Suggestions

[MegaPowerRockstar]

Hi Guys,

I have a below requirement, could you please throw your thoughts how could it be handled....

 

For an instance, we have a record in a database and we have a ui, 2 users are accessing the same record.

When user 1 tries to edit the record and how could user 2 be aware of the change or updated record to be reflected on his screen.

 

Please give your thoughts........

[phoenix_nebula]

as http is stateless.. only polling is the solution

[MegaPowerRockstar]

as http is stateless.. only polling is the solution

 

cant we use application level object...and may be we check if that variable existsand if not read from db...

when we update write it to variable... we can kill it after some time span ...

 

??

[MegaPowerRockstar]

ltt

[phoenix_nebula]

cant we use application level object...and may be we check if that variable existsand if not read from db...

when we update write it to variable... we can kill it after some time span ...

 

??

 

 

u cant hold a ton in application level object. ur server will cry

[MegaPowerRockstar]

u cant hold a ton in application level object. ur server will cry

so wats the solution....

 

i can kill the appObjects by some timeframe....for other user we will check to see if a appobject exists for that record then pull from it....or get from db

[MegaPowerRockstar]

ltt

[phoenix_nebula]

Currently new coming frameworks ... are focussing on developing most of the code to run client side and server side... and also get most of the data on initial load to...client side for efficiency, response time and  performance

The next 5yrs flow will be in this direction .. node js with combination of some frameworks

[phoenix_nebula]

so wats the solution....

 

i can kill the appObjects by some timeframe....for other user we will check to see if a appobject exists for that record then pull from it....or get from db

 

Advanced solution i can think of in this cases is ...i have an architectural solution following MQTT..

With more like publish subscribe ...fashion

[Hyderabad_Nawab]

Maaku same ilaane untadhi.. So in Tibco - We Use Critical Section Group - wer if one Job is Running ..da Second will be Waiting until the First one comoletes the Update..

 

da Same in Other Java Services - vere laaga Handle Chestaaru .. We Use some thing called Version Number @ Each Table.. wen ever oka user record update chesegaane aa version number update ayitadhi.. so inko user same record ni update cheyyali ante he should have same version number in his req - ledha error throw chestadhi like Optimistic Lock Exception.. so general ga every time Find Table chesi latest version number teesukoni appudu updated data ni aa find Output lo merge chesi update chestaaru..

[ParmQ]

Hi Guys,

I have a below requirement, could you please throw your thoughts how could it be handled....

 

For an instance, we have a record in a database and we have a ui, 2 users are accessing the same record.

When user 1 tries to edit the record and how could user 2 be aware of the change or updated record to be reflected on his screen.

 

Please give your thoughts........

 

Bro, nothing to do with front-end. Depends on how DAO layer is written. There are things like pessimistic and optimistic locking and lock modes. If you are using JPA or hibernate or any ORM framework, you use these modes and write a logic in DAO.

 

Look here

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjiu.html

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjhz.html

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjjf.html

 

edited: if you are not using ORM framework, you can still ask the DB to set the concurrency modes for a particular transaction. Its possible using JDBC, I'm not sure what technology you are using for data access.

[Hyderabad_Nawab]

Bro, nothing to do with front-end. Depends on how DAO layer is written. There are things like pessimistic and optimistic locking and lock modes. If you are using JPA or hibernate or any ORM framework, you use these modes and write a logic in DAO.

 

Look here

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjiu.html

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjhz.html

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjjf.html

GP...Eggactly.. maaku Idhe Implementaion...:)

[ParmQ]

GP...Eggactly.. maaku Idhe Implementaion... :)

 

:)  Good to know.

[Hyderabad_Nawab]

:)  Good to know.

:)

[MegaPowerRockstar]

Bro, nothing to do with front-end. Depends on how DAO layer is written. There are things like pessimistic and optimistic locking and lock modes. If you are using JPA or hibernate or any ORM framework, you use these modes and write a logic in DAO.

 

Look here

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjiu.html

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjhz.html

 

http://docs.oracle.com/javaee/6/tutorial/doc/gkjjf.html

 

edited: if you are not using ORM framework, you can still ask the DB to set the concurrency modes for a particular transaction. Its possible using JDBC, I'm not sure what technology you are using for data access.

 

can you guys post some links for dot net related...