Skip to content

Commit 621df8f

Browse files
committed
links to sample applications in README, Archiving README is still incomplete
1 parent 040a375 commit 621df8f

File tree

2 files changed

+233
-0
lines changed

2 files changed

+233
-0
lines changed

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -169,6 +169,14 @@ List<Archive> archives = opentok.listArchives(0, 50);
169169
List<Archive> archives = opentok.listArchives(50, 50);
170170
```
171171

172+
# Samples
173+
174+
There are two sample applications included in this repository. To get going as fast as possible, clone the whole
175+
repository and follow the Walkthroughs:
176+
177+
* [HelloWorld](sample/HelloWorld/README.md)
178+
* [Archiving](sample/Archiving/README.md)
179+
172180
# Documentation
173181

174182
Reference documentation is available at <http://www.tokbox.com//opentok/libraries/server/java/reference/index.html> and in the

sample/Archiving/README.md

Lines changed: 225 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,225 @@
1+
# OpenTok Archiving Sample for Java
2+
3+
This is a simple demo app that shows how you can use the OpenTok Java SDK to create Sessions,
4+
generate Tokens with those Sessions, and then pass these values to a JavaScript client that can
5+
connect and conduct a group chat.
6+
7+
## Running the App
8+
9+
First, add your own API Key and API Secret to the system properties. For your convenience, the
10+
`build.gradle` file is set up for you to place your values into it.
11+
12+
```
13+
run.systemProperty 'API_KEY', '000000'
14+
run.systemProperty 'API_SECRET', 'abcdef1234567890abcdef01234567890abcdef'
15+
```
16+
17+
Next, start the server using Gradle (which handles dependencies and setting up the environment).
18+
19+
```
20+
$ gradle :sample/Archiving:run
21+
```
22+
23+
Or if you are using the Gradle Wrapper that is distributed with the project:
24+
25+
```
26+
$ ./gradlew :sample/Archiving:run
27+
```
28+
29+
Visit <http://localhost:4567> in your browser. Open it again in a second window. Smile! You've just
30+
set up a group chat.
31+
32+
## Walkthrough
33+
34+
This demo application uses the [Spark micro web framework](http://www.sparkjava.com/). It is similar to
35+
many other popular web frameworks. We are only covering the very basics of the framework, but you can
36+
learn more by following the link above.
37+
38+
### Main Application (src/main/java/com/example/ArchivingServer.java)
39+
40+
The first thing done in this file is to import the dependencies we will be using. In this case that
41+
is the Spark web framework, a couple collection classes, and most importantly some classes from the
42+
OpenTok SDK.
43+
44+
```java
45+
import static spark.Spark.*;
46+
import spark.*;
47+
48+
import java.util.Map;
49+
import java.util.HashMap;
50+
51+
import com.opentok.OpenTok;
52+
import com.opentok.exception.OpenTokException;
53+
```
54+
55+
Next, we set up a main class for the application.
56+
57+
```java
58+
public class HelloWorldServer {
59+
60+
// We will set up some class variables here
61+
62+
public static void main(String[] args) throws OpenTokException {
63+
// The application will start here
64+
}
65+
}
66+
```
67+
68+
Next this application performs some basic checks on the environment. If it cannot find the `API_KEY`and
69+
`API_SECRET` system properties, there is no point in continuing.
70+
71+
72+
```java
73+
public class HelloWorldServer {
74+
75+
private static final String apiKey = System.getProperty("API_KEY");
76+
private static final String apiSecret = System.getProperty("API_SECRET");
77+
78+
public static void main(String[] args) throws OpenTokException {
79+
80+
if (apiKey == null || apiKey.isEmpty() || apiSecret == null || apiSecret.isEmpty()) {
81+
System.out.println("You must define API_KEY and API_SECRET system properties in the build.gradle file.");
82+
System.exit(-1);
83+
}
84+
85+
}
86+
}
87+
```
88+
89+
The first thing the application does is to initialize an instance of `OpenTok` and store it as
90+
a static class variable.
91+
92+
```java
93+
public class HelloWorldServer {
94+
95+
// ...
96+
private static final OpenTok opentok = new OpenTok(Integer.parseInt(apiKey), apiSecret);
97+
98+
public static void main(String[] args) throws OpenTokException {
99+
// ...
100+
}
101+
}
102+
```
103+
104+
Now, lets discuss the Hello World application's functionality. We want to set up a group chat so
105+
that any client that visits a page will connect to the same OpenTok Session. Once they are connected
106+
they can Publish a Stream and Subscribe to all the other streams in that Session. So we just need
107+
one Session object, and it needs to be accessible every time a request is made. The next line of our
108+
application simply calls the `OpenTok` instance's `createSession()` method and pulls out the
109+
`String sessionId` using the `getSessionId()` method on the resulting `Session` instance. This is
110+
stored in another class variable. Alternatively, `sessionId`s are commonly stored in databses for
111+
applications that have many of them.
112+
113+
```java
114+
public class HelloWorldServer {
115+
116+
// ...
117+
private static String sessionId;
118+
119+
public static void main(String[] args) throws OpenTokException {
120+
// ...
121+
122+
sessionId = opentok.createSession().getSessionId();
123+
}
124+
}
125+
```
126+
127+
Spark uses the `externalStaticFileLocation()` method to specify which directory to serve static
128+
files from.
129+
130+
```java
131+
public class HelloWorldServer {
132+
133+
// ...
134+
135+
public static void main(String[] args) throws OpenTokException {
136+
// ...
137+
138+
externalStaticFileLocation("./public");
139+
}
140+
}
141+
```
142+
143+
We only need one page, so we create one route handler for any HTTP GET requests to trigger.
144+
145+
```java
146+
public class HelloWorldServer {
147+
148+
// ...
149+
150+
public static void main(String[] args) throws OpenTokException {
151+
// ...
152+
153+
get(new FreeMarkerTemplateView("/") {
154+
@Override
155+
public ModelAndView handle(Request request, Response response) {
156+
157+
// This is where we handle the request and are responsible for returning a response
158+
159+
}
160+
});
161+
162+
}
163+
}
164+
165+
```
166+
167+
Now all we have to do is serve a page with the three values the client will need to connect to the
168+
session: `apiKey`, `sessionId`, and `token`. The first two are available as class variables. The
169+
`token` is generated freshly on this request by calling `opentok.generateToken()`, and passing in
170+
the `sessionId`. This is because a Token is a piece of information that carries a specific client's
171+
permissions in a certain Session. Ideally, as we've done here, you generate a unique token for each
172+
client that will connect.
173+
174+
```java
175+
get(new FreeMarkerTemplateView("/") {
176+
@Override
177+
public ModelAndView handle(Request request, Response response) {
178+
179+
String token = null;
180+
try {
181+
token = opentok.generateToken(sessionId);
182+
} catch (OpenTokException e) {
183+
e.printStackTrace();
184+
}
185+
186+
// Now we have apiKey, sessionId, and token
187+
188+
}
189+
});
190+
```
191+
192+
Now all we have to do is serve a page with those three values. To do so, we put together a Map of
193+
values that our template system (freemarker) will use to render an HTML page. This is done by
194+
returning an instance of `ModelAndView` that groups this map with the name of a view.
195+
196+
```java
197+
get(new FreeMarkerTemplateView("/") {
198+
@Override
199+
public ModelAndView handle(Request request, Response response) {
200+
// ...
201+
202+
Map<String, Object> attributes = new HashMap<String, Object>();
203+
attributes.put("apiKey", apiKey);
204+
attributes.put("sessionId", sessionId);
205+
attributes.put("token", token);
206+
207+
return new ModelAndView(attributes, "index.ftl");
208+
}
209+
});
210+
```
211+
212+
### Main Template (src/main/resources/com/example/freemarker/index.ftl)
213+
214+
This file simply sets up the HTML page for the JavaScript application to run, imports the
215+
JavaScript library, and passes the values created by the server into the JavaScript application
216+
inside `public/js/helloworld.js`
217+
218+
### JavaScript Applicaton (public/js/helloworld.js)
219+
220+
The group chat is mostly implemented in this file. At a high level, we connect to the given
221+
Session, publish a stream from our webcam, and listen for new streams from other clients to
222+
subscribe to.
223+
224+
For more details, read the comments in the file or go to the
225+
[JavaScript Client Library](http://tokbox.com/opentok/libraries/client/js/) for a full reference.

0 commit comments

Comments
 (0)