SLOW .NET client for custom HTTP server
I am using my own HTTP/SOAP server to handle requests. If calling it from
tomcat axis leads to 300 msg/s, calling it from a .NET (C++ Managed) client
leads to 2 msg/s with a CPU 99% idle !
This same .NET client works fine (250 msg/s) with a .NET server. Has anybody
encountered the same pb ?
Are .NET clients requiring a certain type of advanced HTTP exchange to perform
a good job ? Are they "Sleep(500)" instructions in the .NET client code just
to be sure that only .NET server are used ???
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL