Most Backbone tutorials will describe the process of sending RESTful requests to the server. But, how do we capture that data with our server-side framework? How do we know what the request urls are? How do we monitor these requests using Chrome Dev Tools? I'll show you all of that and more in this screencast.
Hopefully, if you'd been struggling to figure out how Backbone can communicate with your server, this video has clarified a few things. Don't forget: if the acronym, REST, only makes you think about taking a nap, be sure to refer here and here to learn more about it.
- CodeIntroduction to Sails.jsDifficulty:BeginnerCompletion Time:Quick
- CodeA Look at the WordPress HTTP API: A ReviewDifficulty:IntermediateOne of the challenges that comes with writing a series about an API - or even part of an API - is that it's hard to cover every aspect of said API without spending too much time diving deep into one part and simultaneously trying not to simply skim across the top of each API without giving enough practical information. Case in point: Throughout the last series, we've been taking a look at the WordPress HTTP API. Specifically, we've covered wp_remote_get and wp_remote_post, and we've done some relatively extensive work with both functions including building example projects. The thing is, there's still a lot of ground that could be covered in the WordPress HTTP API. In the future, we may do an advanced series on more aspects of the API, but for now, let's review everything we've covered in this series.Read More…
- CodeA Look at the WordPress HTTP API: A Brief Survey of wp_remote_postDifficulty:IntermediateIn the first series on the WordPress HTTP API, we took a look at wp_remote_get. Specifically, we took a look at the following aspects of the API: A survey of the function A practical example thereof How to handle the response And understanding the arguments for the function We're going to continue the series on the WordPress HTTP API, but we're going to turn our attention to a second method of the API: wp_remote_post. Throughout the next set of articles, we're going to take a survey of the function to understand what the function offers and why it's useful, a practical example of how to implement it into our work, as well as how to understand the functions and the response that comes from the function. With that said, let's begin our survey of the function.Read More…
- CodeA Look at the WordPress HTTP API: wp_remote_get - the ResponseDifficulty:IntermediateIn this series, we've been taking a look at the wp_remote_get WordPress HTTP API function in order to understand how it works, how we can use it, and the optional arguments that it accepts. From here, we're able to write detailed requests; however, that's only half of it - there's also the response. In the second article, we took a look at what a basic response would look like, how to evaluate it, and how to display it on the screen, but we didn't actually talk about the response in detail. If you're looking to write more advanced requests and write more defensive code, then it's important to understand the data that's sent as a response. In this final article, we're going to do exactly that.Read More…
- CodeBuilding Apps With the Yeoman WorkflowDifficulty:IntermediateCompletion Time:Short
- CodeWorking With Data in Sails.jsDifficulty:IntermediateCompletion Time:Quick