[Aglets-commits] docs manual.tex,1.15,1.16

[Fernando G. T. <fti...@us...>]

Update of /cvsroot/aglets/docs
In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv23418

Modified Files:
	manual.tex 
Log Message:
Minor changes: typos, "me" and "I" to "we", some pagebreaks to avoid "orphan" titles (or text like).

Index: manual.tex
===================================================================
RCS file: /cvsroot/aglets/docs/manual.tex,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- manual.tex	26 Dec 2008 12:26:17 -0000	1.15
+++ manual.tex	13 Jan 2009 19:33:04 -0000	1.16
@@ -905,7 +905,7 @@
 \end{figure}
 
 
-
+\pagebreak
 
 
 \item \textbf{\underline{Retract}}\newline
@@ -1053,6 +1053,8 @@
 To apply all modifications you have done through the above dialog, you have to click on the \textit{OK} button, while the \textit{Close} one will abandon the modifications. The \textit{Restore Defaults} button reset any changes to the Tahiti default.
 
 
+\pagebreak
+
 
 \item \textbf{\underline{Network Preferences}}\newline
 This entry opens a dialog window that allows users to manage
@@ -1164,8 +1166,9 @@
 be explained here; you can find more details on the Java 2
 documentation. Modifications will be applied to the
 \texttt{\~/.aglets/security/aglets.policy} file. \textbf{Please
-take care when using this option, since it does not work always
-right}; thus you should check that the policy file has changed.
+take care when using this option, since it does not always 
+work as expected}; thus you should check that the policy file 
+has changed.
 
 
 
@@ -2668,28 +2671,28 @@
 
 %% LEFT JUST AS A REFERENCE OF WHERE THE CODE WAS...
 
-\section{Code Examples}
-This section provide a few code examples about running aglets.
-The code shown here is meant for a didactic use only, and does
-not pretend to be professional. 
-%Since this manual, the Aglets platform includes more examples
-%than those provided by the official release; all of them are
-%shown here and belong to the package \texttt{examples.goofy}.
-%Please consider that you will find a buil-in aglet only for those
-%code snippets where the package is explicitly indicated.
+%\section{Code Examples}
+%This section provide a few code examples about running aglets.
+%The code shown here is meant for a didactic use only, and does
+%not pretend to be professional. 
+%%Since this manual, the Aglets platform includes more examples
+%%than those provided by the official release; all of them are
+%%shown here and belong to the package \texttt{examples.goofy}.
+%%Please consider that you will find a buil-in aglet only for those
+%%code snippets where the package is explicitly indicated.
 
 
 
-\subsection{A base agent}
-The following class shows a simple aglet that, once loaded, prints a few 
-messages on the standard output (i.e., the console where you launched 
-the \texttt{agletsd} command).
+%\subsection{A base agent}
+%The following class shows a simple aglet that, once loaded, prints a few 
+%messages on the standard output (i.e., the console where you launched 
+%the \texttt{agletsd} command).
 
 
-\subsection{Event Listeners}
+%\subsection{Event Listeners}
 
 
-\subsection{A sleeping aglet}
+%\subsection{A sleeping aglet}
 
 
 %\subsection{Agent Chat}
@@ -2776,13 +2779,13 @@
 \begin{center}
 \begin{verbatim}
 # Unix - Linux
-echo \$CLASSPATH
-echo \$JDK_HOME
-echo \$JAVA_HOME
-echo \$AGLETS_HOME
+echo $CLASSPATH
+echo $JDK_HOME
+echo $JAVA_HOME
+echo $AGLETS_HOME
 
 # Windows
-echo %classpath%
+echo %CLASSPATH%
 echo %JDK_HOME%
 echo %JAVA_HOME%
 echo %AGLETS_HOME%
@@ -2795,7 +2798,8 @@
 
 
 \item \textbf{Are there any public Aglets servers I can send my aglets to?}\newline
-There were a few trials about a public aglet server, but at the best of my knowledge, there is no one server running now.
+There were a few trials about a public aglet server, but at the best of our knowledge, 
+there is no one server running now.
 
 
 
@@ -2854,7 +2858,7 @@
 not take the Aglets related environment variables into account
 by default. You should explicitly put the AGLET\_PATH and 
 AGLET\_EXPORT\_PATH on the java command-line when 
-launching a stand-alone server (as far as I know, at least).
+launching a stand-alone server (as far as we know, at least).
 For example under *nix, if your server is called 
 \texttt{StandAloneServer}:
 \begin{center}
@@ -3005,8 +3009,18 @@
 FIPA means Foundation for Intelligent and Physical Agents, and is a no-profit organization that defines agents' standards, such as communication languages (called ACLs), interoperability protocols, and so on.
 
 \item \textbf{Is Aglets 2.0.2 FIPA compliant?}\newline
-No. Aglets is not FIPA compliant, since it has been developed when FIPA was only a proposal. Furthermore, in those days, there was another standard: the \textit{MASIF} (Mobile Agent Systems Intercommunication Facility). Due to this Aglets is MASIF compliant, even if there is not a lot of documentation (or better, there is no documentation) regarding MASIF in Aglets and how well it works. It must be noticed that Aglets is RMI compliant, thus you can use it in combination with the Java's RMI services.
-Please note that the fact that Aglets is not FIPA compliant does not means that developers do not want that standard, it is simply a developing lack! Maybe one day Aglets will be FIPA compliant....
+No. Aglets is not FIPA compliant, since it has been developed
+when FIPA was only a proposal. Furthermore, in those days, there
+was another standard: the \textit{MASIF} (Mobile Agent Systems
+Intercommunication Facility). Due to this Aglets is MASIF
+compliant, even if there is not a lot of documentation (or
+better, there is no documentation) regarding MASIF in Aglets and
+how well it works. It must be noticed that Aglets is RMI
+compliant, thus you can use it in combination with the Java's RMI
+services. Please note that the fact that Aglets is not FIPA
+compliant does not mean that developers do not want that
+standard, it is simply a developing lack! Maybe one day Aglets
+will be FIPA compliant...
 
 \item \textbf{Is FIPA so important?}\newline
 It is difficult to answer to this question, since it depends on a
@@ -3186,7 +3200,11 @@
 The most efficient way to transform a file into an object depends on what your application must do, and I suggest you to have a look even at the SOAP or any other XML based document form. Finally, please take care that if the file is available by a network filesystem (such as AFP, SMB, NFS), you do not need to migrate the file at all, but simply to adjust the file name on the destination.
 
 \item \textbf{Can I use HTTP messaging among aglets?}\newline
-Please note that you can implement any kind of network messaging in Aglets, from standard sockets, to HTTP, SOAP, RMI, etc. But it is on your own to implement such way of communications; you can have a look at the code available at the aglets-net project(see \texttt{http://sourceforge.net/projects/agletsnet}.
+Please note that you can implement any kind of network messaging
+in Aglets, from standard sockets, to HTTP, SOAP, RMI, etc. But it
+is on your own to implement such way of communications; you can
+have a look at the code available at the aglets-net project (see
+\texttt{http://sourceforge.net/projects/agletsnet}).
 
 \item \textbf{Is there a way to exchange data among agents?}\newline
 Yes, you have to send messages containing the data you want to exchange, but please take care of the serializability of your objects, since the messaging system allows only serializable messages.