One Minute Evaluations for 28-30 January

CS 537 - Client-Server Interfaces

1. Topic: This week we talked about the basics of what is a client-server and how it can be implemented.

   Didn't get: Sockets patterns.

   One minute response: A pattern is anything you've written twenty or thirty times before, usually without realizing it.

2. Topic: We talked about Socket API, different models for communication, history of network, protocols.

   Didn't get: I have [?].

3. Topic: About client ans server and basic level TCP and UDP.

   Didn't get: How to implement with sockets.

   One minute response: We'll haven't gotten to that yet. We'll spend the rest of the semester talking about that.

4. Topic: Introduction to TCP and sockets.

   Didn't get: Difficult in understanding why use UDP.

   One minute response: We haven't talked about that yet, but on the plus side UDP is cheaper than TCP and preserves message boundries. On the minus side.

5. Topic: We talked about the various protocols in the TCP/IP stack and about the API.

   Didn't get: The endpoint and connections, i.e. undefined unresolved and resolved is confused.

   One minute response: If I tell you only to call some person on the phone, the phone number you should is undefined (which number?). If I tell you to call some person in Long Branch, the number is defined (some number in Long Branch), but unresolved (which number in Long Branch?). If I tell you to call me, the number is both defined and resolved.

6. Topic: TCP/IP fundamentals, how the internet works, client server approach.

   Didn't get: Undefined, unresolved, and sockets (understood little bit).

   One minute response: Understanding endpoints; a socket is just an implementation of the endpoint abstraction.

7. Topic: We spoke about TCP, UDP and their implementation, API.

   Didn't get: I cannot actually visualize the implementation as a code. Probably too early I guess.

8. Topic: UDP and TCP.

   Didn't get: I got a fair idea what the UDP and TCP are. Class was good.

   One minute response: Thanks.

9. Topic: Sockets API, C-S patterns, distributed/client-server programming, IP suite.

   Didn't get: Till today things were easy to understand.

   One minute response: And it's all down hill from here.

10. Topic: Client & server, TCP, IP addresses, sockets, UDP.

    Didn't get: Socket, UDP, & port number assignments.

11. Topic: Establishing connection between client and server and data transmission between them.

    Didn't get: I think I am getting through!!!.

12. Topic: TCP/IP & Socket.

    Didn't get: Sockets is little bit difficult to understand.

    One minute response: Only a little? The trick is to work with a few simple patterns and then expand from there when you' comfortable.

13. Topic: TCP/IP protocol detail, Socket API.

    Didn't get: I think almost everything is clear.

14. Topic: We have learned about Socket APIs.

    Didn't get: Difficult part was the connection set-up part of TCP.

    One minute response: The important thing to know about TCP set-up is that it's expensive for short duration communications.

15. Topic: TCP/IP protocol detail, socket API.

    Didn't get: I think almost everything is clear.

16. Topic: Parallel, distributed, concurrent programming. The bandwidth of the three; how it is actually done. TCP/IP, sockets, endpoints, history.

This page last modified on 1 February 2003.