Replied: Sat, 21 Sep 2002 15:04:23 -0500 Replied: "Hasan Bulut" Return-Path: hbulut@indiana.edu Delivery-Date: Sat Sep 21 13:32:21 2002 Return-Path: Received: from julesburg.uits.indiana.edu (julesburg.uits.indiana.edu [129.79.1.75]) by grids.ucs.indiana.edu (8.10.2+Sun/8.10.2) with ESMTP id g8LIWLm16760 for ; Sat, 21 Sep 2002 13:32:21 -0500 (EST) Received: from logchain.uits.indiana.edu (logchain.uits.indiana.edu [129.79.1.77]) by julesburg.uits.indiana.edu (8.12.1/8.12.1/IUPO) with ESMTP id g8LIWReP007616; Sat, 21 Sep 2002 13:32:27 -0500 (EST) Received: from bozdag (bozdag.ucs.indiana.edu [156.56.104.17]) by logchain.uits.indiana.edu (8.12.1/8.12.1/IUPO) with SMTP id g8LIWRW6021410; Sat, 21 Sep 2002 13:32:27 -0500 (EST) Message-ID: <002901c2619d$9b817eb0$1168389c@bozdag> From: "Hasan Bulut" To: "Geoffrey Fox" References: <002201c2615d$d1c5f720$6f42de0c@computer> <3D8CAF84.1020700@grids.ucs.indiana.edu> Subject: Re: ppt for session server Date: Sat, 21 Sep 2002 13:35:06 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01C26173.B289E4F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Length: 4190 This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C26173.B289E4F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >is what you call web server interface=20 the web service interface Web Server is a component in our system. It is responsible for = displaying web pages and for receiving requests from those pages. We = called the interface in the session server as "web server interface", to = indicate that it sends/receives XML messages to/from Web Server. = Currently we use TCP/IP connections between components in the system to = send/receive XML messages.=20 >Are all XML ports "user-facing" or some to other programs Currently all XML ports are between components of our system. But any = developer can build a component that can send/receive messages to/from = session server as long as it obeys the XGSP format. Clients can only use = our system by dialing from a polycom device and by registering from the = web interface, if he wants to use web interface. Regards, Hasan Hasan Bulut wrote: I have attached some ppt slides about session server. Please let me = know if you need more detail about session server and its implementation. Thanks, Hasan --=20 : : Geoffrey Fox gcf@indiana.edu FAX 8128567972 : Phones Cell 315-254-6387 Home 8123239196 Lab 8128567977 CS 8128553788 ------=_NextPart_000_0026_01C26173.B289E4F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

>is what you call web server interface
the web service=20 interface

Web Server is a component in our = system. It is=20 responsible for displaying web pages and for receiving requests from = those=20 pages. We called the interface in the session server as "web server = interface",=20 to indicate that it sends/receives XML messages to/from Web Server. = Currently we=20 use TCP/IP connections between components in the system to send/receive = XML=20 messages.

>Are=20 all XML ports "user-facing" or some to other programs

Currently all XML ports are between = components of=20 our system. But any developer can build a component that can = send/receive=20 messages to/from session server as long as it obeys the XGSP=20 format. Clients can only use our system by dialing from a = polycom=20 device and by registering from the = web interface,=20 if he wants to use web interface.

Regards,

Hasan

Hasan Bulut wrote:

I have attached some ppt slides = about session=20 server. Please let me know if
you need more detail about session = server=20 and its implementation.

Thanks,
Hasan

--=20
:
: Geoffrey Fox  gcf@indiana.edu FAX 8128567972
: Phones Cell 315-254-6387 Home 8123239196 Lab 8128567977 CS =
8128553788

------=_NextPart_000_0026_01C26173.B289E4F0--