archivesspace-api-workshop/26-ArchivesSpace-API-Workshop.html at master · rockivist/archivesspace-api-workshop · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
<!DOCTYPE html>
<html>
<head>
   <link href="css/slides.css" rel="stylesheet" />
</head>
<body>
	<nav>
<a id="start-slide" rel="nav" href="00-ArchivesSpace-API-Workshop.html" title="Return to start of presentation">Start</a>
<a id="prev-slide" rel="nav" href="25-ArchivesSpace-API-Workshop.html" title="Previous slide">Prev</a>
<a id="next-slide" rel="nav" href="27-ArchivesSpace-API-Workshop.html" title="Next slide">Next</a>
	</nav>
	<section><h1>3. Authentication</h1>

<h2>Some words about encoding</h2>

<p>The web is organized around plain text and socket connections
between computers. We can not ship the data as it is in our computer&rsquo;s
memory to the other computer for lots of reasons. What we do
is translate it (encode it) in a predictable way.  A common way on
the web is &ldquo;urlencoding&rdquo;. Another type of encoding that has become
populate in recent years is JSON.  That&rsquo;s the encoding style we&rsquo;ll
use most often in our API requests but for authentication we use
&ldquo;urlencoding&rdquo;.</p>

<p>The final encode reference in our previous example was to &lsquo;utf-8&rsquo;. This
refers to a character encoding. They way we represent symbols
like letters or characters in other langauages like Danish, Hindi or
Korean. JSON by specification expects to be &lsquo;utf-8&rsquo;</p>

<p>So in one case we encode our data into an expected layout and in
another we explicitly encode it into a character representation.
Both are important.</p>
</section>
   <script type="text/javascript" src="js/keyboard-nav.js"></script>
</body>
</html>