I/O Multiplexing: The idea of I/O multiplexing is to use “select” function to ask kernel to suspend process. It returns control to application only after one or more I/O events had occurred. It denotes waiting for a set of descriptors that is ready for reading. The “select” function would manipulate sets of type “fd_set”, that denotes descriptor sets. It takes two inputs: a descriptor set called “read set” and cardinality of read set. It blocks until at least one descriptor in read set is ready for reading. A descriptor “k” is ready for reading if and only if a request to read 1 byte from that descriptor would not block. The “fd_set” is been modified that points to argument “fdset” to indicate subset of read set called “ready set”. The value returned by function indicates cardinality of ready set.

Question

Want to see the full answer?

Answer 1

Question

Chapter 12, Problem 12.23HW

Program Plan Intro

I/O Multiplexing:

The idea of I/O multiplexing is to use “select” function to ask kernel to suspend process.

It returns control to application only after one or more I/O events had occurred.

It denotes waiting for a set of descriptors that is ready for reading.

The “select” function would manipulate sets of type “fd_set”, that denotes descriptor sets.

It takes two inputs: a descriptor set called “read set” and cardinality of read set.

It blocks until at least one descriptor in read set is ready for reading.

A descriptor “k” is ready for reading if and only if a request to read 1 byte from that descriptor would not block.

The “fd_set” is been modified that points to argument “fdset” to indicate subset of read set called “ready set”.

The value returned by function indicates cardinality of ready set.

Expert Solution & Answer

Want to see the full answer?

Check out a sample textbook solution

See solution

Students have asked these similar questions

Computer Science C programming Develop a proxy HTTP server that can accept HTTP requests from clients and convert them to HTTPS request to the web server. The HTTP request can be filtered based on an access control list. The requests can be generated by any web client, such as the curl command or a web browser. the proxy converts plain text HTTP requests from a client to HTTPS requests and then returns the responses to the client. Main objective is to create a proxy HTTP server that converts cleartext HTTP requests from clients to HTTPS requests to servers and vice versa for the responsesresponses.

Currently, the web server handles only one HTTP request at a time. Implement a multithreaded server that is capable of serving multiple requests simultaneously. Using threading, first create a main thread in which your modified server listens for clients at a fixed port. When it receives a TCP connection request from a client, it will set up the TCP connection through another port and services the client request in a separate thread. There will be a separate TCP connection in a separate thread for each request/response pair.

An issue that we have glossed over so far is how the client locates the server in remote procedural calls. One method is to hardwire the network address of the server into the client. The trouble with this approach is that it is extremely inflexible. If the server moves or if the server is replicated or if the interface changes, numerous programs will have to be found and recompiled. To avoid this limitation, which kind of binding is appropriate to match up clients and servers? Also explain basic procedure of such binding. OO 6:46 PM