Java 9 SE for Impatient: HTTP/2

[A Kao]

I enjoyed reading your previous Java books.
How complete is your new book Java 9 SE for Impatient HTTP/2 coverage?
I downloaded your source codes.
I see HttpClientDemo.java, which is good.
I do not see HTTP/2 Push, ... example.

[Cay Horstmann]

Hi, it's good feedback that you want HTTP/2 push covered.

Generally, I stick to use cases that (a) aren't bleeding edge and (b) are of interest to application programmers, not system programmers. If in a year or two, application programmers have to worry about this, I'll put it into the book.

I think it's an important skill to eyeball a new feature and gauge whether it has a broad impact. For example, someone who should remain nameless (Simon Ritter) gives presentations about new features in Java 9 that contain such gems as "PKCS12 key stores by default" and "Spin-Wait Hints". These are important features only for the small number of heroes who give us application programmers better-performing libraries and tools. The service that I aim to provide is that I don't put them in my books.

Of course, I am sometimes wrong, so if you feel that I am missing the boat on an important feature, let me know.

Cheers,

Cay

[Stephan van Hulst]

I think you do a fantastic job at writing to a target audience. I think if I was an author, I would constantly forget who my audience is and go on about things *I* think are interesting.

[Campbell Ritchie]

How on earth would a reader want to read anything we don't think interesting?

[Tim Cooke]

One of the main things I like about Core Java SE9 for the Impatient is the very fact that Cay has curated a collection of topics that don't necessarily cover every aspect of the Java language. Rather he has included everything you need for what I would consider to be solid general purpose programming. These are the skills and knowledge that a working Software Engineer needs in her day to day life to write good quality code that solves problems in a straight forward manner. Edge cases, quirks, and obscurities are rightfully (in my opinion) omitted, and even the section on the Reflection library is introduced with a healthy dose of caution. I think the book is all the better for it.

[A Kao]

Cay Horstmann wrote:Hi, it's good feedback that you want HTTP/2 push covered.

Generally, I stick to use cases that (a) aren't bleeding edge and (b) are of interest to application programmers, not system programmers. If in a year or two, application programmers have to worry about this, I'll put it into the book.

I think it's an important skill to eyeball a new feature and gauge whether it has a broad impact. For example, someone who should remain nameless (Simon Ritter) gives presentations about new features in Java 9 that contain such gems as "PKCS12 key stores by default" and "Spin-Wait Hints". These are important features only for the small number of heroes who give us application programmers better-performing libraries and tools. The service that I aim to provide is that I don't put them in my books.

Of course, I am sometimes wrong, so if you feel that I am missing the boat on an important feature, let me know.

Cheers,

Cay

I am a Java web services developer.
RESTful Web Services builds upon HTTP, so I am curious how the HTTP/2 (e.g. push) features in Java will affect web services, especially RESTful ones.
Will you write a book about Java web services in the future?

[Cay Horstmann]

When I first saw the new HTTP client, I had high hopes that it would come with support for REST. At the very least, a JSON content handler. But nooo...I was told that JSON was not a part of the core platform, so that not something they'd sully their hands with. The HTTP client doesn't do forms or file upload either. This is one of the few times that I may end up breaking my own rules and cover a non-core API in Core Java. But I don't think I'll write a whole book on REST.

Cheers,

Cay

[A Kao]

Cay Horstmann wrote:When I first saw the new HTTP client, I had high hopes that it would come with support for REST. At the very least, a JSON content handler. But nooo...I was told that JSON was not a part of the core platform, so that not something they'd sully their hands with. The HTTP client doesn't do forms or file upload either. This is one of the few times that I may end up breaking my own rules and cover a non-core API in Core Java. But I don't think I'll write a whole book on REST.

Cheers,

Cay

Does "a whole book" mean 500+ pages?
Your "Java SE8 for the Really Impatient" book is 240 pages.   Will you write a short book on REST for similar page counts in the future?

[Cay Horstmann]

A Kao wrote:
Does "a whole book" mean 500+ pages?
Your "Java SE8 for the Really Impatient" book is 240 pages.   Will you write a short book on REST for similar page counts in the future?

Many years ago, I wrote a college textbook on object-oriented design. A book reviewer of Dr. Dobb's Journal (the young ones won't know what that was) wrote "Horstmann is a man of few words", and it was meant as a compliment. I could maybe write a 100 page book on REST programming, but I marvel at the authors who can stretch it out to 300+ pages. I think I'll leave that to them, and add a quick introduction into a future edition of Core Java.

Cheers,

Cay

[Paul Clapham]

Cay Horstmann wrote:Many years ago...

In those days you had to write thick books, because they were easier to be seen by people looking at shelves in a bookstore. The thicker the book, the easier it was to see. But the days of people walking through bookstores looking for technical books are gone, so the books can be right-sized again.

[Cay Horstmann]

That is so true. It motivated me to write "Java SE 8 for the Really Impatient". And I just saw "Java EE 8--Only What's New". BTW, with a bonus HTTP/2 chapter. I couldn't resist and bought it.

Cheers,

Cay

[Campbell Ritchie]

Paul Clapham wrote:. . . thick books . . . were easier to be seen by people looking at shelves in a bookstore. . . . .

Hahahahahahahahahahahahahahaha!

Horstmann and Cornell was always amongst the ranks of thick books. Very slightly thicker than a Deitel book of similar vintage.