Re: SOAP applicable in this scenario ?

From: Hugo Pragt (hcgpragt_at_hotmail.com)
Date: 01/26/04 

Date: Mon, 26 Jan 2004 18:58:58 +0100

Hi, here's my two pence:

1) SOAP is an expensive protocol, I don't know how many UDP packets per
second you are planning to process, but maybe you want something less
expensive (=CPU consuming)..

2) When all your clients run a SOAP server, you can push the SOAP envelopes
to them, instead of them polling the server. This is almost anythime a
better scaleable solution.

3) If you have A LOT of clients you can make some or all of them subhosts,
creating your own DNS like network for forwarding information.

"Tristan" <shiranaihito@hotmail.com> wrote in message
news:9b593766.0401260712.20a511a2@posting.google.com...
> Hi,
>
> first the case:
> I want to implement a distributed application (client/server
> architecture).
> The server collects UDP packets from somewhere else. The client or
> clients must somehow get these packets from the server in real time. I
> mean if there are UDP packets coming to the server, the server should
> immediately forward these packets to each client. It would be a great
> thing if the clients could be behind a firewall, so that no network
> settings are needed (e.g. open certain ports). So my idea was to use
> SOAP as communication protocol.
> The problem is that I have to do permanently SOAP RPCs to ask the
> server if there are new packets. I think that's not so good,
> especially if there are many clients, I get performance problems. Is
> there a solution to solve the problem of real time passing of
> information with SOAP ?
>
> Thank you.
>
> Bye, Tristan.

Relevant Pages

  • SOAP Message receiving
    ... using SOAP and am not sure on the best way to implement the server. ... My first preference was Axis (as one of the clients are using it - the other ...
    (comp.lang.java.programmer)
  • Re: Events between machines
    ... > destination queues at the same time without relying on IP multicasting. ... > I've attached the source code for a small client and a small server to ... >> Assume one server and several clients, all on the same subnet (datalayer ... >> regarding how the clients (which are listening for these udp packets) ...
    (microsoft.public.dotnet.framework.remoting)
  • Events between machines
    ... Don't use events (callback) between machine, ... Assume one server and several clients, all on the same subnet (datalayer is ... Assume the server send small udp packets without actual data, ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Events between machines
    ... The problem with UDP is that it is generally not reliable. ... would also work if no single event would ever reach the clients. ... Windows Server 2003) which allows you to send a message to multiple ... > regarding how the clients (which are listening for these udp packets) ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: XML-string transportieren
    ... > Server ist JAVA, die clients sind C#. Hintergund ist der, dass auf den ... > vom Server zu den Clients und umgekehrt? ... Ich dachte an SOAP, habe aber keine ... Webservice, der per WSDL seine Dienste definiert, eine Proxy-Klasse zu ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)