ive written a little chat system, but would like to discuss the organisation.
the chat is serverbased. all clients have to connect to the server via tcp/ip and then they get an overview about the other clients (but no direct connection). so all actions (color changes etc) and messages are first sent to the server and then directed to the other clients.
the messages are concatenated with a command, e.g.:
change_color||red
say||greetings!
and cut into command - operation via stringtokenizer.
so my questions:
the work for my server is very hard, he has to accept EVERY action. situations like one client doesnt want to hear another is handled with a filter system by the server,
so he gets messages, which are perhaps obsolete.
is this the normal chat-architecture ?
or should i code only a server which arranges the direct-connections between the clients, so if a clients logs into the network it gets all ips from the other clients for connection ?