470,819 Members | 1,604 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,819 developers. It's quick & easy.

Multiple client connections advise

Hi,

I'm about to embark on a project that will both send and receive information
to/from our client computers in the field.

The area that I still need to finalize is the method of communication and
the technology to use.

The following will be true:

1. Communications will need to be over the internet and each client will
have a continuous connection to the internet (DSL or cable modem), but its
IP address could fluctuate.
2. We cannot connect to our clients due to firewall considerations, so the
client must connect to our server.

3. There could between 100 and 2000 clients
4. The remote clients will need to send information to our server.
5. We will need to be able to send information to our clients with a
reasonable delay (a minute or so is fine), so the client will either have to
check in frequently with the server or remain connected for long periods of
time.
6. Communications must be secure


I have started looking at WSE 3 and it looks like a good option for
communication and will allow us to integrate easily with WCF in the future.
However, I'm not sure how well web services using WSE can handle hundreds of
multiple client connections.

Can a WSE web service handle multiple connections (on the order of 1000 or
more) at the same time?

Is it a better idea to have the client check in once a minute or just stay
connected to the server?

Should I be considering some other technology?

Any help from those that may have some experience in these matters would be
much appreciated.


Dave


Oct 16 '06 #1
3 2051
"D. Yates" <fo****@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
Hi,

I'm about to embark on a project that will both send and receive
information to/from our client computers in the field.

The area that I still need to finalize is the method of communication and
the technology to use.

The following will be true:

1. Communications will need to be over the internet and each client will
have a continuous connection to the internet (DSL or cable modem), but its
IP address could fluctuate.
2. We cannot connect to our clients due to firewall considerations, so
the client must connect to our server.

3. There could between 100 and 2000 clients
4. The remote clients will need to send information to our server.
5. We will need to be able to send information to our clients with a
reasonable delay (a minute or so is fine), so the client will either have
to check in frequently with the server or remain connected for long
periods of time.
6. Communications must be secure


I have started looking at WSE 3 and it looks like a good option for
communication and will allow us to integrate easily with WCF in the
future. However, I'm not sure how well web services using WSE can handle
hundreds of multiple client connections.

Can a WSE web service handle multiple connections (on the order of 1000 or
more) at the same time?

Is it a better idea to have the client check in once a minute or just stay
connected to the server?

Should I be considering some other technology?

Any help from those that may have some experience in these matters would
be much appreciated.
I would look at either Web Services or Remoting. Both styles will be
supported in WCF.

I would not maintain connections which will largely be idle, unless there's
s substantial setup time for the connections. For instance, if
authentication is expensive and only lasts for a single connection, then you
might want to keep the connection open.

Otherwise, let the client connect when it needs to. The Web Services
infrastructure will do this for you.

John
Oct 16 '06 #2
John,

Thanks for your reply.

If my clients don't use a continuous connection with my web service and
check in every 30 - 60 seconds to see if they need to do some work, what
suggestion do you have for this scenario?

I'm thinking that I could setup two web services. One web service (A)
accepts the periodic check in from the clients and lets them know if they
need to connect to the other web service (B) and accept some work based upon
a flag in a database. Connections to web service A would NOT be secure (to
reduce overhead) and connections to web service B would be secure and
provide the client with some work via a secure tunnel.

Thoughts?

Dave
Oct 16 '06 #3
"D. Yates" <fo****@hotmail.comwrote in message
news:uL**************@TK2MSFTNGP05.phx.gbl...
John,

Thanks for your reply.

If my clients don't use a continuous connection with my web service and
check in every 30 - 60 seconds to see if they need to do some work, what
suggestion do you have for this scenario?

I'm thinking that I could setup two web services. One web service (A)
accepts the periodic check in from the clients and lets them know if they
need to connect to the other web service (B) and accept some work based
upon a flag in a database. Connections to web service A would NOT be
secure (to reduce overhead) and connections to web service B would be
secure and provide the client with some work via a secure tunnel.

Thoughts?
This makes sense.

John
Oct 17 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by Quiet Man | last post: by
1 post views Thread by VITAS | last post: by
1 post views Thread by VITAS | last post: by
2 posts views Thread by jasonsgeiger | last post: by
35 posts views Thread by keerthyragavendran | last post: by
5 posts views Thread by Chamnap | last post: by
reply views Thread by mihailmihai484 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.