|
-
Jul 9th, 2003, 09:51 AM
#9
Thread Starter
Fanatic Member
what about multicasting? i'm not sure what exactly this is, but it sounds like it may help me...
basically here's the structure:
the app has a server and client part to it... the client part is simple, doesn't need to be multithreaded or anything, i only want to send out one message at a time...
the server part needs to be multithreaded as it could be receiving messages from multiple clients at a time...
what i'm thinking of doing now, is making a tcplistener open all the time.. it accepts sockets and listens to each socket on it's own thread... since connections won't be maintained, this should be a quick process. each thread basically accepts a message and then that connection to the client is closed...
the client of course is simple, i connect to the desired host, send a message, and disconnect, then i'm ready to send another message...
any thoughts?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|