Home
Asynchronous vs Synchronous Ajax
June 2, 2014
14 Comments

Asynchronous vs Synchronous Ajax

Synchronous 

Script stops and waits for the server to send back a reply before continuing. There are some situations where Synchronous Ajax is mandatory.

In standard Web applications, the interaction between the customer and the server is synchronous. This means that one has to happen after the other. If a customer clicks a link, the request is sent to the server, which then sends the results back.

Because of the danger of a request getting lost and hanging the browser, synchronous javascript isn’t recommended for anything outside of (onbefore)unload event handlers, but if you need to hear back from the server before you can allow the user to navigate away from the page, synchronous Javascript isn’t just your best option.

Asynchronous vs Synchronous Ajax

Asynchronous

Where the script allows the page to continue to be processed and will handle the reply if and when it arrives. If anything goes wrong in the request and/or transfer of the file, your program still has the ability to recognize the problem and recover from it.
Processing asynchronously avoids the delay while the retrieval from the server is taking place because your visitor can continue to interact with the web page and the requested information will be processed with the response updating the page as and when it arrives.

Asynchronous vs Synchronous
<<Previous <<   || Index ||   >>Next >>

 

Previous
Next
AJAX

Related Posts

About The Author

Dinesh Rajput

Dinesh Rajput is the chief editor of a website Dineshonjava, a technical blog dedicated to the Spring and Java technologies. It has a series of articles related to Java technologies. Dinesh has been a Spring enthusiast since 2008 and is a Pivotal Certified Spring Professional, an author of a book Spring 5 Design Pattern, and a blogger. He has more than 10 years of experience with different aspects of Spring and Java design and development. His core expertise lies in the latest version of Spring Framework, Spring Boot, Spring Security, creating REST APIs, Microservice Architecture, Reactive Pattern, Spring AOP, Design Patterns, Struts, Hibernate, Web Services, Spring Batch, Cassandra, MongoDB, and Web Application Design and Architecture. He is currently working as a technology manager at a leading product and web development company. He worked as a developer and tech lead at the Bennett, Coleman & Co. Ltd and was the first developer in his previous company, Paytm. Dinesh is passionate about the latest Java technologies and loves to write technical blogs related to it. He is a very active member of the Java and Spring community on different forums. When it comes to the Spring Framework and Java, Dinesh tops the list!

14 Comments

  1. brijesh July 3, 2014

    thanks.. It's working for me.

  2. Java Lover @ 135 July 16, 2014

    Great Post!!

  3. vergin July 17, 2014

    thanks buddy..

  4. Viswanathan Saravanan September 9, 2014

    Hi dinesh, how action error messages are captured without in employee.jsp?

  5. Dinesh Rajput September 9, 2014

    Another option is we can use simple error map and return to view end with error message.

  6. Viswanathan Saravanan September 9, 2014

    Hi Dinesh,
    To make it very correct please add method="addEmployee" which is missing in

  7. Dinesh Rajput September 9, 2014

    Thanks Viswanathan for this correction.

  8. Nelson October 15, 2014

    Thank you very much

  9. Dinesh Rajput October 16, 2014

    thanks

  10. Dinesh Rajput October 16, 2014

    Thanks Shiva!!!

  11. Nguyễn Văn Sơn January 21, 2015

    Thank you! Your post's amazing!

  12. Dinesh Rajput January 22, 2015

    Thanks!!!

  13. Bruno Maia Serralheiro February 5, 2015

    Dear Dinnesh, if you still get the same exception after being careful with the case sensitiveness, what might be the problem?

  14. Bruno Maia Serralheiro February 5, 2015

    I would like to share my experience about this issue: for @Entity and @Table avoid hibernate annotation.

    Use JPA (javax.persistence) instead:
    import javax.persistence.Entity;
    import javax.persistence.Table;

    It took me a day to see this silly mistake one time.

    Congratulations for this post.

    Best Regards!