Jorge Godoy <[EMAIL PROTECTED]> writes: > How can you get to answer to 2 simultaneous clients on the same port at the > same time without multicast/broadcast then? Threads allow you to run > concurrent things but they don't magically turn your physical medium into > something that can carry more information at the same time.
There's no need for physical medium here, you can only answer one request at a time on each port, this is what I was trying to say. I was thinking on another thing that involved more bandwidth, this is why there appeared the physical constraint on my message. Even with threads, you can't handle two different things at the very same time on the same port. And there's one process listening or writing to the port at a given time. If multiple threads request the information from this server process, the server is acting as a multiplexer. If forking -- I haven't read CP's code and I wasn't thinking specifically about it even tho it is the one that was involved -- them each process can bind to a port and handle everything from there, without the need of a multiplexer. -- Jorge Godoy <[EMAIL PROTECTED]>
