X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C71B2A.27941C35@onstor-exch02.onstor.net>; Fri, 8 Dec 2006 16:37:06 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C71B2A.27941C35"
Content-class: urn:content-classes:message
Subject: Cougar: web server?
Date: Fri, 8 Dec 2006 16:37:06 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E01AA3CDA@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar: web server?
thread-index: AccbKidrWEY0vS9cS46IX/ZJ2KijpA==
From: "Charissa Willard" <charissa.willard@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C71B2A.27941C35
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Andy,

=20

The sscccc daemon is used to process requests for both the web-ui and
NGM. This daemon is a wrapper around the current cli code in ssc-nfxsh.
The code for sscccc is in sm-sct.=20

=20

We use simple XML request and response headers to wrap the cli commands
and their output. The responses contain a single string with the output
of the cli. We will be replacing this daemon and need to come up with an
alternative. For the web-ui, port 443 is used (HTTPS). Perhaps we can
start thinking about using a lightweight web server or something a bit
just a bit more efficient then the sscccc daemon. Note that sscccc
spawns an nfxsh for every request. Also, the nfxsh will be going away.
NGM support currently isn't required for Cougar, so no need to worry
about it. Let me know if you have any thoughts on this issue.

=20

=20

Thanks,

Charissa

=20

=20


------_=_NextPart_001_01C71B2A.27941C35
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'>Andy,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'>The
sscccc daemon is used to process requests for both the web-ui and NGM. =
This
daemon is a wrapper around the current cli code in ssc-nfxsh. The code =
for
sscccc is in sm-sct. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'>We
use simple XML request and response headers to wrap the cli commands and =
their
output. The responses contain a single string with the output of the =
cli. We
will be replacing this daemon and need to come up with an alternative. =
For the
web-ui, port 443 is used (HTTPS). Perhaps we can start thinking about =
using a lightweight
web server or something a bit just a bit more efficient then the sscccc =
daemon.
Note that sscccc spawns an nfxsh for every request. Also, the nfxsh will =
be
going away. NGM support currently isn&#8217;t required for Cougar, so no =
need
to worry about it. Let me know if you have any thoughts on this =
issue.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'>Charissa<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:9.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C71B2A.27941C35--
