The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

infos@wais-fr.com (29) [Avatar] Offline
#1
Some remarks about 1.2.3 HTTP API wrappers

Sorry but I do not understand the term HTTP API. For me HTTP API is a term related to HTML5 set of Specs designed by the W3C (like Web Socket API, Geolocalization API, ...)

Figure 1.4 is confusing since there is no clear clues that indicate where are the Servers and where is the Client Browser.
This Figure should be redesigned

About the LinkedIn HTTP API example :
Listing 1.3 conveys only Javascript code that is labeled HTTP API. It is quite confusing: if listing 1.3 is about HTTP API, what is the difference between HTTP API and third-party Javascript (listing 1.1)?

My suggestion :
1°) Avoid using the term HTTP API
2°) Figure 1.4 should be the first Figure in this chapter. The left part of this figure should be labeled : the Old Way (doing all processing server-side), the right part of the figure should be labeled : the modern Way (injecting high/low-level functionalities from external server)

Best regards
benvinegar (68) [Avatar] Offline
#2
Re: About Chapter 1 (1.2.3 HTTP API wrappers)
Hi Henri,

Those are fair comments. I was thinking of using "Web Service APIs" instead of "HTTP APIs". Is that clearer?
infos@wais-fr.com (29) [Avatar] Offline
#3
Re: About Chapter 1 (1.2.3 HTTP API wrappers)
Yes I think "Web Service APIs" should be a replacement for HTTP API wrappers