Book Image

Angular Services

Book Image

Angular Services

Overview of this book

A primary concern with modern day applications is that they need to be dynamic, and for that, data access from the server side, data authentication, and security are very important. Angular leverages its services to create such state-of-the-art dynamic applications. This book will help you create and design customized services, integrate them into your applications, import third-party plugins, and make your apps perform better and faster. This book starts with a basic rundown on how you can create your own Angular development environment compatible with v2 and v4. You will then use Bootstrap and Angular UI components to create pages. You will also understand how to use controllers to collect data and populate them into NG UIs. Later, you will then create a rating service to evaluate entries and assign a score to them. Next, you will create "cron jobs" in NG. We will then create a crawler service to find all relevant resources regarding a selected headline and generate reports on it. Finally, you will create a service to manage accuracy and provide feedback about troubled areas in the app created. This book is up to date for the 2.4 release and is compatible with the 4.0 release as well, and it does not have any code based on the beta or release candidates.
Table of Contents (15 chapters)
Angular Services
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Introducing the Google Custom Search Engine


As we saw in Chapter 3, The Collector Service - Using Controllers to Collect Data, not every website is open to HTTP requests coming from unknown sources. We experienced cross-origin resource sharing (CORS) issues before and we saw how to use Yahoo APIs to work around it. So what we need here is a list of links related to searched keywords. Assembling a URL which uses Google to search for keywords is easy. What is not easy is passing that search result to the Yahoo API for extracting the contents. If you do that, you will get an "access denied" response from Google.

That makes sense because if Google people don't set any control over the source and number of queries that hit their servers, they will be vulnerable and a few lines of code can put a lot of pressure on, or even crash, their servers. Basically, what they say is: you are welcome to use our search engine in browser/mobile applications but if you are going to make requests via code or command...