This is an automated email from the ASF dual-hosted git repository.

andreww pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/royale-docs.git


The following commit(s) were added to refs/heads/develop by this push:
     new 47073ba  Update security.md
47073ba is described below

commit 47073ba1566a34ae42e51d9c3974e9a6a35e437e
Author: Andrew Wetmore <[email protected]>
AuthorDate: Thu Feb 1 19:06:32 2018 -0400

    Update security.md
    
    Small changes in text and layout.
---
 create-an-application/application-tutorial/security.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/create-an-application/application-tutorial/security.md 
b/create-an-application/application-tutorial/security.md
index c79ba7d..c3008b5 100644
--- a/create-an-application/application-tutorial/security.md
+++ b/create-an-application/application-tutorial/security.md
@@ -20,11 +20,16 @@ title: Application security
 
 # Application security
 
-There are two sides to security:  How do you access something external 
resource?  And, How do you keep certain external resources from accessing your 
application and the things your application can access.  There is a separate 
section that deals with both topics in more detail, but the most common 
problem, especially for applications that mainly present data instead of 
collect data, is how to access an external resource.
+There are two sides to security:  
 
-It is up the external resource to decide whether you can access it or not.  
And even if the external resource intends to let others access it, there may be 
rules and restrictions in order to get permission.  If you run into an access 
problem, look for documentation on "Cross-Origin Resource Sharing" or "CORS".
+1. How do you access and get data or other material from an external source?
+2. How do you keep certain external sites, processes or people from accessing 
your application and the things your application can access?
 
-Fortunately, for this tutorial, GitHub's APIs are very permissive and the 
application should now show rows of commits if it wasn't when running from 
file://.
+There is a separate section that deals with both topics in more detail, but 
the most common problem, especially for applications that mainly present data 
instead of collecting data, is how to access an external resource.
+
+It is up the external resource to decide whether you can access it or not. And 
even if the external resource intends to let others access it, there may be 
rules and restrictions about who can get permission, and under what conditions. 
 If you run into an access problem, look for documentation on "Cross-Origin 
Resource Sharing" or "CORS".
+
+Fortunately, for this tutorial, GitHub's APIs are very permissive. Once you 
have your application on a website it should now show rows of commits even if 
it wasn't when running from file://.
 
 {:align="center"}
 [Previous Page](create-an-application/application-tutorial/debug.html) \| 
[Next Page](create-an-application/application-tutorial/production.html)

-- 
To stop receiving notification emails like this one, please contact
[email protected].

Reply via email to