Jump to content

Talk:IBM Advanced Program-to-Program Communication: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
No edit summary
Line 1: Line 1:
Is it true that in TCP/IP one partner is always a server and the other always a client? The only way I can see this being the case is that one machine must listen for a connection while the other initiates the communication - however once a TCP channel is up there's no client/server distinction inherent in the protocol. I'd suggest that this page only gets to make such a statement if AAPC *doesn't* work like that - ie if it doesn't have the notion of listening for a connection. However, I can't conceive of any other mechanism for doing networking. [[Special:Contributions/195.212.29.83|195.212.29.83]] ([[User talk:195.212.29.83|talk]]) 12:14, 25 April 2008 (UTC)
Is it true that in TCP/IP one partner is always a server and the other always a client? The only way I can see this being the case is that one machine must listen for a connection while the other initiates the communication - however once a TCP channel is up there's no client/server distinction inherent in the protocol. I'd suggest that this page only gets to make such a statement if AAPC *doesn't* work like that - ie if it doesn't have the notion of listening for a connection. However, I can't conceive of any other mechanism for doing networking. [[Special:Contributions/195.212.29.83|195.212.29.83]] ([[User talk:195.212.29.83|talk]]) 12:14, 25 April 2008 (UTC)


The link is dead. --[[Special:Contributions/217.195.52.165|217.195.52.165]] ([[User talk:217.195.52.165|talk]]) 19:21, 26 April 2008 (UTC)
The link is dead.

Revision as of 19:21, 26 April 2008

Is it true that in TCP/IP one partner is always a server and the other always a client? The only way I can see this being the case is that one machine must listen for a connection while the other initiates the communication - however once a TCP channel is up there's no client/server distinction inherent in the protocol. I'd suggest that this page only gets to make such a statement if AAPC *doesn't* work like that - ie if it doesn't have the notion of listening for a connection. However, I can't conceive of any other mechanism for doing networking. 195.212.29.83 (talk) 12:14, 25 April 2008 (UTC)[reply]

The link is dead. --217.195.52.165 (talk) 19:21, 26 April 2008 (UTC)[reply]