"D. Yates" <foeman@hotmail.com> wrote in message
news:%23$ZIPfU8GHA.1252@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.

"D. Yates" <foeman@hotmail.com> wrote in message
news:uLljSyU8GHA.2268@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?