By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,344 Members | 1,147 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,344 IT Pros & Developers. It's quick & easy.

Messages

P: n/a
Thank you in advance for reading this.
I need to have two applications send messages over the network to each
other. Basically one server application and (possibly) many client
applications. I am using VS 2003. What choices do I have when it comes
to implementing this. I am currently using (and it is working) the
TcpClient but would like to know what other choices are out there.

Thanks again!

Oct 30 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
"It depends". It depends on your requirements for what would be a good
choice for sending messages.

I have a solution that has many distributed client applications and one
central server. In my scenario I need to have messages routed from one
client to another and I need to make sure that the messages arrive. To
accomplish that I use MSMQ. It is quite trivial and has more than
adaquate performance for what I need. The solution works by each
client registering themselves with the server via a well known private
queue name. When the server needs to communicate to a client it looks
up its computer name and sends a message to the client on a well know
client queue name.

There are more choices but you would be well served to identify more of
your requirements.

Steve

unwantedspam wrote:
Thank you in advance for reading this.
I need to have two applications send messages over the network to each
other. Basically one server application and (possibly) many client
applications. I am using VS 2003. What choices do I have when it comes
to implementing this. I am currently using (and it is working) the
TcpClient but would like to know what other choices are out there.

Thanks again!
Oct 30 '06 #2

P: n/a

FishingScout wrote:
"It depends". It depends on your requirements for what would be a good
choice for sending messages.

I have a solution that has many distributed client applications and one
central server. In my scenario I need to have messages routed from one
client to another and I need to make sure that the messages arrive. To
accomplish that I use MSMQ. It is quite trivial and has more than
adaquate performance for what I need. The solution works by each
client registering themselves with the server via a well known private
queue name. When the server needs to communicate to a client it looks
up its computer name and sends a message to the client on a well know
client queue name.

There are more choices but you would be well served to identify more of
your requirements.

Steve

unwantedspam wrote:
Thank you in advance for reading this.
I need to have two applications send messages over the network to each
other. Basically one server application and (possibly) many client
applications. I am using VS 2003. What choices do I have when it comes
to implementing this. I am currently using (and it is working) the
TcpClient but would like to know what other choices are out there.

Thanks again!


Steve,
Thank you for your response. Basically what needs to be done is the
following:
Client sends a message to the server. Based on what is in the message,
the server will perform an action (update db, write text file, send
email,...) Then the sever sends a message back to the client stating
success or failure.

I would greatly appreciate any feed back you might have based on this
information.

Thanks again.

Oct 30 '06 #3

P: n/a
unwantedspam,

It sounds like one option would be to use a Web Service.

Kerry Moorman
"unwantedspam" wrote:
>
FishingScout wrote:
"It depends". It depends on your requirements for what would be a good
choice for sending messages.

I have a solution that has many distributed client applications and one
central server. In my scenario I need to have messages routed from one
client to another and I need to make sure that the messages arrive. To
accomplish that I use MSMQ. It is quite trivial and has more than
adaquate performance for what I need. The solution works by each
client registering themselves with the server via a well known private
queue name. When the server needs to communicate to a client it looks
up its computer name and sends a message to the client on a well know
client queue name.

There are more choices but you would be well served to identify more of
your requirements.

Steve

unwantedspam wrote:
Thank you in advance for reading this.
I need to have two applications send messages over the network to each
other. Basically one server application and (possibly) many client
applications. I am using VS 2003. What choices do I have when it comes
to implementing this. I am currently using (and it is working) the
TcpClient but would like to know what other choices are out there.
>
Thanks again!

Steve,
Thank you for your response. Basically what needs to be done is the
following:
Client sends a message to the server. Based on what is in the message,
the server will perform an action (update db, write text file, send
email,...) Then the sever sends a message back to the client stating
success or failure.

I would greatly appreciate any feed back you might have based on this
information.

Thanks again.

Oct 30 '06 #4

P: n/a

Kerry Moorman wrote:
unwantedspam,

It sounds like one option would be to use a Web Service.

Kerry Moorman
"unwantedspam" wrote:

FishingScout wrote:
"It depends". It depends on your requirements for what would be a good
choice for sending messages.
>
I have a solution that has many distributed client applications and one
central server. In my scenario I need to have messages routed from one
client to another and I need to make sure that the messages arrive. To
accomplish that I use MSMQ. It is quite trivial and has more than
adaquate performance for what I need. The solution works by each
client registering themselves with the server via a well known private
queue name. When the server needs to communicate to a client it looks
up its computer name and sends a message to the client on a well know
client queue name.
>
There are more choices but you would be well served to identify more of
your requirements.
>
Steve
>
unwantedspam wrote:
Thank you in advance for reading this.
I need to have two applications send messages over the network to each
other. Basically one server application and (possibly) many client
applications. I am using VS 2003. What choices do I have when it comes
to implementing this. I am currently using (and it is working) the
TcpClient but would like to know what other choices are out there.

Thanks again!


Steve,
Thank you for your response. Basically what needs to be done is the
following:
Client sends a message to the server. Based on what is in the message,
the server will perform an action (update db, write text file, send
email,...) Then the sever sends a message back to the client stating
success or failure.

I would greatly appreciate any feed back you might have based on this
information.

Thanks again.

Kerry,
Thank you for your feedback. I had thought of using a web service. The
issue I had was how do I tell that the server has finished processing.
Would I need to "pull" the web service on a set interval.

Any further information on using this approach would be greatly
appreciated.

Thanks Again!

Oct 30 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.