Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying RESTful Java Web Services
  • Table Of Contents Toc
  • Feedback & Rating feedback
RESTful Java Web Services

RESTful Java Web Services

By : Bogunuva Mohanram
4.8 (5)
close
close
RESTful Java Web Services

RESTful Java Web Services

4.8 (5)
By: Bogunuva Mohanram

Overview of this book

Representational State Transfer (REST) is a simple yet powerful software architecture style to create lightweight and scalable web services. The RESTful web services use HTTP as the transport protocol and can use any message formats, including XML, JSON(widely used), CSV, and many more, which makes it easily inter-operable across different languages and platforms. This successful book is currently in its 3rd edition and has been used by thousands of developers. It serves as an excellent guide for developing RESTful web services in Java. This book attempts to familiarize the reader with the concepts of REST. It is a pragmatic guide for designing and developing web services using Java APIs for real-life use cases following best practices and for learning to secure REST APIs using OAuth and JWT. Finally, you will learn the role of RESTful web services for future technological advances, be it cloud, IoT or social media. By the end of this book, you will be able to efficiently build robust, scalable, and secure RESTful web services using Java APIs.
Table of Contents (18 chapters)
close
close
Title Page
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Representing date and time in RESTful web resources


Here is a list of recommendations when you have the date (and time) fields in the RESTful web API resources:

  • ISO 8601 is the International Standard for the representation of dates and times. It is recommended to use the ISO-8601 format for representing the date and time in your RESTful web APIs. Here is an example for the ISO-8601 date and time: YYYY-MM-DDThh:mm:ss.sTZD (for example, 2015-06-16T11:20:30.45+01:00).
  • The API that you build must be capable of accepting any time zone set by the client.
  • While storing the date and time fields present in the resource representation in the database, use Coordinated Universal Time (UTC). UTC is guaranteed to be consistent.
  • While retuning the date and time fields in response to an API call, use the UTC time zone. The client can easily convert the date field present in the resource into the desired local time by using an appropriate UTC offset.

Limited Time Offer

$10p/m for 3 months

Get online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech and supported with AI assistants

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY