RE: Web Services or Sockets?

You might want to consider using Web Services via WSE 2.0. It becomes a
simple thing to start a listener at one end and post data to it in the form
of SOAP envelopes. It certainly would be far more extensible if you use a
push architecture as you will be able to support far more clients. In terms
of the issues involved with ports and firewalls/NAT, there is some very
pertinent information about this being written regarding SOAP routing
protocols. There will always be issues though if you decide to move away from
port 80 traffic however as you still require the specific ports to be open.

SQL Notification services would certainly be one way to achieve the pub/sub
scenario however will not relieve the issues related to firewalls/NAT. It is
also something that is certainly not a requirement to support this type of
scenario.

I would be looking at some of the newer specification work with regard to
SOAP routers, WS-Eventing etc. as this would offer you an extensible method
of delivering info to your clients using standards so you get the bits of Web
Services that make it simple to use and the ability to support sockets etc.
via WSE 2.0.


"Joe" wrote:

> I am looking to create a Windows Forms application that would get
> notifications from the server when data changes or it gets an instant message
> from other users. This application would have to work at different sites
> over the internet. The two technologies I am looking at are Web Services or
> Sockets. Would it be okay to have a client (lets say 500 clients) poll a web
> service every 5 seconds for messages? The messages will be stored in a MSMQ
> queue on the server and returned to the client through the web service
> call. This is the direction I would like to go for several reasons. Reason
> one; I don’t have to worry about the socket programming. Reason two is that
> some of the clients might be mobile going in and out of coverage breaking the
> socket connection.
>
> So my question is will polling the service be too much network traffic?
> Does polling a web service utilize more server recourses then streaming
> sockets? I am thinking it will, but I am hoping somebody will tell me
> otherwise!
>
> Thanks for any help or information!
>
.

Relevant Pages

  • Re: Architectural feedback
    ... Create your smart clients as std winforms apps using c# or VB. ... will call web services server to get lists, updates, etc. ... Most functionality will be accessed from our ...
    (microsoft.public.dotnet.general)
  • Re: Alternative to Remoting?
    ... you use WS with your custom objects without any problem? ... ready for serve them back to the clients. ... >> I thought about using web services, but they doesn't mantain the table ... > reader doesn't have a lot of properties, but you could do the same with ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: remoting cross platform compatibility
    ... Yes, it is possible to have multiple channels, e.g. ... However, if you're thinking of using non-.NET clients, then I'd recommend ... as if they are web services involves some extensions to SOAP that are likely ... > what i exactly need to change in my server config file ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: How do Large Scale Web Service Applications Maintain Session State?
    ... create a stateful server session. ... There are session sweepers and all sorts ... Having systems deployed through web services allows clients to access via ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Is there an easy way to query a remote xml file by not using web services? (Windows and Unix)
    ... You need to do a little more reading on web services. ... > server versus the web server initiating contact with the clients. ... >>> the xml file here every so often automatically, or I use SQL and just ...
    (microsoft.public.dotnet.languages.csharp)
Loading