What problems do you foresee in the direct coupling between communicating entities that is implicit in remote invocation approaches? Consequently, what advantages do you anticipate from a level of decoupling as offered by space and time uncoupling?
What will be an ideal response?
The client is intrinsically bound to the server and vice versa and this is inflexible in terms of dealing with failure, for example if the server fails and a backup server takes over managing requests. More generally, this level of coupling makes it hard to deal with change.
Clients and servers must exist at the same time and hence it is not possible to operate in more volatile environments when either party may be unavailable, for example disconnected in the case of a mobile node.
The benefits of space uncoupling is in providing more degrees of freedom in dealing with change, for example if a new server starts dealing with requests.
The benefit of time uncoupling is in allowing entities to communicate when entities may come and go.
You might also like to view...
Describe folders and libraries and give examples of each.
What will be an ideal response?
Dictionary attacks and brute force attacks can be blocked by locking systems after incorrect passwords are used
Indicate whether the statement is true or false
In the code for the __init__ method in the Entry class or a dictionary, what is the missing code?
def __init__(self, key, value):
A. key = self.key B. self.key = key C. value = self.key D. self.key = value
You're working in Vi and, after having saved your current file, you want to load a new one. You can do so by typing ____ newfile.txt from command mode.
Fill in the blank(s) with the appropriate word(s).