Update of /cvsroot/asterisk-java/asterisk-java/xdocs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8044/xdocs
Modified Files:
design.xml
Log Message:
Fixed typos (thanks to Tobias Wolf for providing a patch)
Index: design.xml
===================================================================
RCS file: /cvsroot/asterisk-java/asterisk-java/xdocs/design.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -p -r1.2 -r1.3
--- design.xml 11 Jul 2005 17:58:10 -0000 1.2
+++ design.xml 15 Jul 2005 08:47:09 -0000 1.3
@@ -41,8 +41,8 @@
Asterisk starts. Your application is then tightly
coupled to Asterisk but has access to any internal
structure.</p>
- <p>The second approach is to write AGI scripts. An AGI
- script is to Asterisk what a CGI script is to an
+ <p>The second approach is to write AGI (Asterisk Gateway Interface)
+ scripts. An AGI script is to Asterisk what a CGI script is to an
HTTP server. You can think of AGI as a means to
make your dialplan more dynamic by handing control
to an external process. As with CGI in its early
@@ -59,8 +59,8 @@
<p>The third approach is to use Asterisk's Manager API.
The Manager API allows an external application to
query and change Asterisk's state by sending actions
- and listening to responses and events. Comminication
- occors via TCP/IP. Compared to AGI the Manager API
+ and listening to responses and events. Communication
+ occurs via TCP/IP. Compared to AGI the Manager API
works without the need to operate on a concrete call
(in Asterisk parlance a channel).</p>
<p>The last approach is to talk to Asterisk via IAX
@@ -70,9 +70,9 @@
In contrast to AGI and the Manager API IAX allows
passing media streams, for example sending and
receiving audio.</p>
- <p>Regarding the first approach a JNI based solution
- (JAsterisk) is available that spawns a Java Virtual
- Machine from within Asterisk and exposes Asterisk's
+ <p>Regarding the first approach a JNI (Java Native Interface)
+ based solution (JAsterisk) is available that spawns a
+ Java Virtual Machine from within Asterisk and exposes Asterisk's
internal API. Development of JAsterisk seems to be
discontinued. Due to the involved tight coupling this
approach is questionable anyway.</p>
@@ -95,7 +95,7 @@
<p>Flexible means you should be able to use it in a variety
of different environments, like standalone Java GUI
applications running on a user's desktop, servlets running
- in a JEE servlet container, Java webstart applications,
+ in a J2EE servlet container, Java webstart applications,
or maybe even applets if anybody is still using them.
Being flexible also means you should have access to any
feature exposed by the corresponding Asterisk interface
@@ -104,7 +104,7 @@
extend Asterisk-Java to support additional features.
This extensibility is important when you choose to run a
modified version of Asterisk that supports additional
- actions and events through the Manager API or addtional
+ actions and events through the Manager API or additional
commands via AGI.</p>
<p>Robust means you can focus on your own
application and rest asured that Asterisk-Java "just
|
