|
m e e t i n g . n o t e s
|
|
Asynchronous/Synchronous in the sense that: opening a socket, sending data, closing socket vs opening a socket, sending data, waiting, receiving data, closing socket.
- Synchronous:
good: one open and one close call, everything done in one. From security point of view: One party has only to connect, this can enhance security. sort of sequential, easy to keep track of what is going on.
bad: if one party has to wait the connection still stays up and waits and waits. This open, waiting, socket uses some resources as it needs a permanent sort of "connection is still up but wait some more" messages. Error prone to when the network goes down or ip addresses change etc. if the connection is open for a long time (which can be the case in ebXML).
- Asynchronous:
good: open, do business, then close. proper open then close. no waiting during a connection.
bad: Both parties have to connect to each other service. eg firewalls on both sides need open ports. difficult to keep track of what is going on. Many different state machines at the server side and one incoming message has to be mapped to one state machine. Also the sequence of the messages (not in the ebXML space but generally) can be out of order and the server has to make sure it can handle out of order, or any order messages.
| |
| Why would a company prefer FTP over HTTP or vice verca? E.g there can be security aspects but also administrative aspects as one company does not want to do anything with ftp as there is a big maintenance job to be done etc. | |
| Security is an obvious concern of the above comments. Also it might be possible that a company does not trust company x so they want to have maximum security with company x but on the other hand they are more relaxed with company z. | |
| | |
| | |
| | |
|
|