end.html
Warning: This file has been marked up for HTML
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Author" content="Novell">
<meta name="GENERATOR" content="Mozilla/4.61 [en] (Win98; U) [Netscape]">
<title>Novell Chat - Conclusion</title>
</head>
<body>
<center><font size=+4><font face="Arial,Helvetica"><font color="#990000">Novell
</font></font><font color="#000000">Chat</font></font>
<br><font face="Arial,Helvetica"><font color="#000000"><font size=+2>for</font></font></font>
<br><font face="Arial,Helvetica"><font color="#666666"><font size=+3>ConsoleOne</font></font></font>
<p><font size=+2>Conclusion</font></center>
<p><br>
<p>Writing snapins for ConsoleOne is not meant to be difficult. In
fact, it's not hard at all. At first it may seem confusing as you
struggle to learn the API, but once you do, you will see how simple it
can become. ConsoleOne not only provides you with a common environment
to plug your applications into, but it also provides you with an easy way
to access NDS. With those two critical parts taken care of, all you
need to worry about is the application itself.
<p>The purpose of this example is to show you exactly how this can all
be done. We took a widely know concept (Chatting) and transformed
it into a directory enabled application. The directory made it easier
to locate users and chat rooms and it provided a means by which a user's
identity could be verified to allow secure chatting.
<p>The tools are all there, but it's up to you to put them to work.
<br>
<center>
<p><<a href="code.html">Previous</a> <a href="index.html">Contents</a></center>
</body>
</html>