Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Node.js Web Development

You're reading from  Mastering Node.js Web Development

Product type Book
Published in Jun 2024
Publisher Packt
ISBN-13 9781804615072
Pages 778 pages
Edition 1st Edition
Languages
Author (1):
Adam Freeman Adam Freeman
Profile icon Adam Freeman
Toc

Table of Contents (26) Chapters close

1. Putting Node.js in Context
2. Getting Ready 3. Working with the Node.js Tools 4. JavaScript and TypeScript Primer 5. Understanding Node.js Concurrency 6. Handling HTTP Requests 7. Using Node.js Streams 8. Using Bundles and Content Security 9. Unit Testing and Debugging 10. Node.js in Detail
11. Creating the Example Project 12. Using HTML Templates 13. Handling Form Data 14. Using Databases 15. Using Sessions 16. Creating RESTful Web Services 17. Authenticating and Authorizing Requests 18. SportsStore
19. SportsStore: A Real Application 20. SportsStore: Navigation and Cart 21. SportsStore: Orders and Validation 22. SportsStore: Authentication 23. SportsStore: Administration 24. SportsStore: Deployment 25. Other Books You May Enjoy
26. Index

Updating data

There are two ways to support updates in web services: replacing data and patching data. An HTTP PUT request is sent when the client wants to completely replace data, and the request body contains all of the data the web service will need for the replacement. An HTTP PATCH method is used when the client wants to modify data, and the request body contains a description of how that data should be modified.

Supporting updates with PUT requests is simpler to implement but requires the client to provide a complete replacement for the stored data. PATCH requests are more complex but offer more flexibility and can be more efficient because only the changes are sent to the web service.

Tip

It can be hard to know which approach to adopt at the start of a new project when the types of updates clients will send are unknown. My advice is to start by supporting complete updates because they are simpler to implement and move to partial updates only if you find...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime