Many thanks, gentlemen, for Your help.
I think, I should go further on the bridging path.
Having the clients equipped with an asynchronic-listening window
and having all connections open until the server terminates the arrangement works.
The only problem is the lack of a good theoretical handbook concerning these questions, that is not -as always- a hidden tutorial about C++!
Thanks again
Heinz Grandjean
Announcement
Collapse
No announcement yet.
Communication between clients
Collapse
X
-
Originally posted by Heinz Grandjean View PostMy question: would it be possible to have two clients (!) getting in contact with each other using this multithreaded server as (let us say) a brigde??
You can also have a many-to-many relationship without a central server (think BitTorrent). But in this situation, you do have to deal with firewall issues.
Leave a comment:
-
In re the fundamental question...
Or do I missunderstand TCP??
However, I agree with the business-soundness (and maintenance-soundness!) of a design which features a single server as a 'traffic cop.'
I would probably agree with the 'security-soundness', too, but I don't do security.
Leave a comment:
-
Originally posted by Michael Mattias View PostBut if they were, why even keep the server in the loop as a "bridge" when the two clients can connect and talk directly?
It can also address security and permissions related issues; since all messages must pass through the server, it can monitor and filter them as appropriate. For example, the server can have code that looks for clients who are sending a high volume of messages and throttle them, preventing other clients from getting swamped (or preventing an outright denial-of-service attack). It also allows for a centralized authentication and policy mechanism, rather than having each client being responsible for determining if another client should be allowed to talk to it, and what kind of messages they should be able to send.
Leave a comment:
-
Why not?
Client to server: "I'm here"
Server to Client: "Cool. Here's who else is here: Name/IPAddress, Name/IPAddress ...."
However, clients are probably not prepared to accept a call except in response to a server request.
But if they were, why even keep the server in the loop as a "bridge" when the two clients can connect and talk directly?
Of course, that makes clients servers, too.
It's a thought.
Leave a comment:
-
Communication between clients
Hello PB-Community,
I' ve learned that a multiple server is able to hold connection to more than one client simultaneously. So far OK; my test-sample seems to work reliable.
My question: would it be possible to have two clients (!) getting in contact with each other using this multithreaded server as (let us say) a brigde??
Or do I missunderstand TCP??
Thanks for help,
Heinz GrandjeanTags: None
Leave a comment: