socket problem chat?

Thread view:

Enable EMail Alerts

Start New Thread

Marc Collin - 07 Dec 2005 04:17 GMT

hi

i would like to know how in a application client/server how we send received
message to all client?

thanks

Reply to this Message

Chris Smith - 07 Dec 2005 04:35 GMT

> i would like to know how in a application client/server how we send received
> message to all client?

In general, there are two ways. One is to use multicast. The other is
to individually send the message to each client. Unless you're dealing
with a very large number of clients, it's probably best to do the
latter. Just keep a list of clients, and write a list to send messages
to each one... perhaps each in a different thread to control the delay.

Signature

www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation

Reply to this Message

Marc Collin - 07 Dec 2005 15:59 GMT

>> i would like to know how in a application client/server how we send
>> received message to all client?
[quoted text clipped - 4 lines]
> latter. Just keep a list of clients, and write a list to send messages
> to each one... perhaps each in a different thread to control the delay.

ok for the second method but we need to connect to the client
the client need to be a server..

Reply to this Message

Roedy Green - 07 Dec 2005 20:07 GMT

On Wed, 07 Dec 2005 10:59:13 -0500, Marc Collin
<collinm@laboiteaprog.com> wrote, quoted or indirectly quoted someone
who said :

>ok for the second method but we need to connect to the client
>the client need to be a server..

Or:
1. UDP
2. every client maintains a socket
3. clients check in with HTTP every "minute" or so to see if there is
a massage.

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.

Reply to this Message

Chris Smith - 07 Dec 2005 20:21 GMT

> ok for the second method but we need to connect to the client
> the client need to be a server..

When you establish a TCP connection from a client to the server, that
connection is two-way. The server can use it to send data to the
client. That's why java.net.Socket has methods called getInputStream()
and getOutputStream().

If your client disconnect, though, then yes they will need a
ServerSocket to listen for reconnection attempts from the server (and
this is also problematic because many -- or most? -- clients won't have
publicly available ports.)

Signature

www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation

Reply to this Message

zero - 07 Dec 2005 20:48 GMT

Chris Smith <cdsmith@twu.net> wrote in news:MPG.1e00f21c1bd135c4989c00
@news.altopia.net:

>> ok for the second method but we need to connect to the client
>> the client need to be a server..
[quoted text clipped - 8 lines]
> this is also problematic because many -- or most? -- clients won't have
> publicly available ports.)

Typically it's the client that connects to the server. The server just
sits, waiting for clients to connect. If you need the server to connect to
the client (instead of the other way around) you may want to rethink your
design.

Signature

Beware the False Authority Syndrome

Reply to this Message

Roedy Green - 07 Dec 2005 09:11 GMT

On Tue, 06 Dec 2005 23:17:06 -0500, Marc Collin
<collinm@laboiteaprog.com> wrote, quoted or indirectly quoted someone
who said :

>i would like to know how in a application client/server how we send received
>message to all client?

Consider using UDP. You can even then have clients send direct to each
other.

see http://mindprod.com/jgloss/udp.html

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.

Reply to this Message

socket problem chat?

Free Magazines