Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
RESTful Java Web Services

You're reading from   RESTful Java Web Services A pragmatic guide to designing and building RESTful APIs using Java

Arrow left icon
Product type Paperback
Published in Nov 2017
Publisher
ISBN-13 9781788294041
Length 420 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Balachandar Bogunuva Mohanram Balachandar Bogunuva Mohanram
Author Profile Icon Balachandar Bogunuva Mohanram
Balachandar Bogunuva Mohanram
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Introducing the REST Architectural Style 2. Java APIs for JSON Processing FREE CHAPTER 3. Introducing the JAX-RS API 4. Advanced Features in the JAX-RS APIs 5. Introducing JAX-RS Implementation Framework Extensions 6. Securing RESTful Web Services 7. Description and Discovery of RESTful Web Services 8. RESTful API Design Guidelines 9. The Role of RESTful APIs in Emerging Technologies 10. Useful Features and Techniques

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...
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 $19.99/month. Cancel anytime