[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster] Annoying Warning about recv failed
Hi Marcel, I originally started out trying to port the java applet to c#, but I ran into some
problems and abandoned it.. (my programming skills are limited.. ha ha). Anyway,
the webservice is a good option for me because the client (written in any language) does not
need to know anything about the underlying messaging system just the appropriate calls
to the webservice. Hence, I could use Java and C# together and not care about including the
proper xmlblaster libraries.
Also, the c# client has callback capabilities. It is basically a fire-and-forget type of call
to the webservice. When the result is returned, a method is called on the c# client program
that passes the data from the webservice (similar to the xmlblaster update method).
I did some testing and found that my work computer (a p4 3ghz with 1gb ram) doesn't throw
these recv failed warnings as much (about once every 20 or so messages) as my test server. My test
server is an antiquated p2 266mhz with 192mb of ram and a 4 gig hard drive :-)
The only difference between these two machines (besides the hardware) is the test server is
running java 1.5 update 10 and my work computer is running java 1.5 update 6. All other software
is the same.
----- Original Message ----
From: Marcel Ruff <mr at marcelruff.info>
To: xmlblaster at server.xmlBlaster.org
Sent: Wednesday, January 24, 2007 8:28:03 AM
Subject: Re: [xmlblaster] Annoying Warning about recv failed
i couldn't follow all of it :-)
I can offer our native C# wrapper (calling the C client lib) which connects
over the SOCKET protocol and tunnels callbacks back (compressed with
in real time.
It works very well on Windows, Windows CE (Smartphone/PocketPC/Mobile) and
If it is only the port which counts you can put the xmlBlaster server on
port 80, but
if it must be http traffic this wont help.
Further you can use some of our servlets and look at the (tiny) applet
code how to talk to them. Then implement the same client code in C#.
Finally your approach sounds nice as well, but as you don't have a callback
possibility you need to poll from C# (which is not too problematic on
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around