One Minute Evaluations for 18-20 February

CS 537 - Client-Server Interfaces

• Topic: This week we talked about CGI and SOAP..

  Didn't get: Both are too complicated..

  One minute response: The XML-RPC developers agreed with you on SOAP..

• Topic: HTTP, CGI, SGML.

  Didn't get: What is CGI and why need it?.

  One minute response: CGI is a way for HTTP servers to hand-off resource management to the system on which the server is running..

• Topic: we talked about HTTP, HTML, XML, CGI mechanism.

  Didn't get: Everything seems to be ok if some self reading is done..

• Topic: CGI architecture XML, DTD.

  Didn't get: How to create parser. Is there parsers available?.

  One minute response: Oh yes; go to www.freshmeat.net and search for them..

• Topic: Taught: HTML, CGI, HTTP.

  Didn't get: Difficult; CGI.

  One minute response: CGI is so simple that people tend to make it too complicated..

• Topic: HTTP, CGI, XML, SGML, SOAP..

  Didn't get: I need to try out SOAP and CGI..

  One minute response: Because SOAP is text-based, you might have an easier time of it using Perl or TCL or some other language suited to text manipulation..

• Topic: We got good idea how SOAP makes our lives easy. Good to know about HTTP..

  Didn't get: Can you explain with an example how to implement SOAP..

  One minute response: Sure..

• Topic: We learned about HTML and CGI.

  Didn't get: Not clear:-> How to actually write code for CGI..

  One minute response: Follow the links on the syllabus for more CGI information..

• Topic: We spoke about HTTP 1.0/1.1, CGI, SGML, XML, and the evolution of HTML and XML and the DTD concept..

  Didn't get: I do not understand the standardization part for this..

  One minute response: Standards represent a common language (in theory, anyway). If everyone speaks their own language, nobody can communicate..

This page last modified on 25 March 2003.