request input on client/server design

Hi there,

I'm considering doing a project that involves collaborative client/server application involving chat, whiteboard, VoiP, etc.

My question is this...would each aspect of the project (chat, whiteboard,etc) require that it run on a seperate port to the server? Is that normal from a design perspective? I'm thinking a seperate thread on the server listening on different ports: one for the chat (port 2000), one for the whiteboard(port 2001), one for VoiP(port 2002), etc.

I'm only thinking of this approach as being favourable because the types of data being moved back and forth would be different on each port. Does this make sense? Are there some other approaches to this type of project?

Alan

[738 byte] By [ashiersa] at [2007-11-27 2:11:51]
# 1
Hi,The easiest thing is to use one port per service/protocol but that also makes it harder to deploy. Some companies might accept to open one port but not three.Kaj
kajbja at 2007-7-12 2:05:30 > top of Java-index,Java Essentials,Java Programming...
# 2

Well then, if it is necessary to use only one port. How does one delegate subsystems to handle the incoming data? Is there some sort of pattern I should be following for this? If so, then is there a tutorial or something you can direct me to?

Alan

Message was edited by:

ashiers

ashiersa at 2007-7-12 2:05:30 > top of Java-index,Java Essentials,Java Programming...
# 3
What you want is to multiplexe your communication into one port. An elegant way to create a communication protocol is to use a stack of protocole layers. I suggest you to take a look here http://www.jgroups.orgHope this help
furtive_minda at 2007-7-12 2:05:30 > top of Java-index,Java Essentials,Java Programming...