8000 update · ninjayoto/Java-Coding-Problems@0cf244e · GitHub
[go: up one dir, main page]

Skip to content

Commit 0cf244e

Browse files
committed
update
1 parent 1a71ab4 commit 0cf244e

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

Chapter13/README.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
1-
# Optional
2-
This chapter includes 24 problems meant to draw several rules for working with **Optional**. The problems and solutions presented in this section
3-
are based on the Brian Goetz (Java’s language architect) definition: *Optional is intended to provide a limited mechanism for library method
4-
return types where there needed to be a clear way to represent “no result," and using null for such was overwhelmingly likely to cause errors.*
5-
But, where there are rules there are exceptions as well. Therefore, do not conclude that the rules (or practices) presented here should be
6-
followed (or avoided) at all costs. Like always, it’s an it depends problem that requires to evaluate the situation and weight pros and cons.
1+
# The HTTP Client and WebSocket APIs
2+
This chapter includes 20 problems that are meant to cover the HTTP Client and WebSocket APIs.
3+
4+
Do you remember HttpUrlConnection? Well, JDK 11 comes with the HTTP Client API as a reinvention of HttpUrlConnection.
5+
The HTTP Client API is easy to use and supports HTTP/2 (default) and HTTP/1.1. For backward compatibility, the HTTP Client API
6+
will automatically downgrade from HTTP/2 to HTTP 1.1 when the server doesn't support HTTP/2. Moreover, the HTTP Client API
7+
supports synchronous and asynchronous programming models and relies on streams to transfer data (reactive streams). It also
8+
supports the WebSocket protocol, which is used in real-time web applications to provide client-server communication with low
9+
message overhead.

0 commit comments

Comments
 (0)
0