Thanks for going into detail for me!
On Monday, February 6, 2017 at 8:57:23 PM UTC-8, Kevin Powick wrote: > > > On Monday, 6 February 2017 23:37:15 UTC-5, so.q...@gmail.com wrote: >> >> >> You said that Node is not required. But I thought react components are >> actually JavaScript objects. >> > > They are. They execute on the client side, in the web browser. > > > >> Would my Golang API server be responding back to requests with those >> JavaScript objects for the React library to render on the client's browser? >> > > > Your Go API service would be responding with data (presumably from a > database), formatted as JSON. The data would have been requested by the > React objects executing in the client browser. > > *Example* > > Suppose you have a Go service that returns details about a customer for a > given a customer ID. The endpoint might be an HTTP GET request that looks > like the following > > http://myService/customer/123456 > > The details are returned in JSON format > > {"Id":123456,"Name":"Bob Smith","Age":25} > > > On the client side, you would have used JavaScript/React to make the API > Call (HTTP GET) and populate your React object with the returned data, > which would then be rendered in your browser UI (page). > > The advantage of your Go service simply returning JSON data is that it can > be consumed by any client software capable of an HTTP request. This make > it available to any number of languages with HTTP Client libraries > available. These days, that's pretty much any language you would care to > work with. > > -- > Kevin Powick > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
