I’m surprised noone here has mentioned long-polling. Long polling means keeping an open connection for a longer period (say 30-60 seconds), and once it’s closed, re-opening it again, and simply having the socket/connection listen for responses. This results in less connections (but longer ones), and means that responses are almost immediate (some may have to … Read more
Check out Apache Axis. That is my all times favorite SOAP implementation. It’s SOAP done right! Exists for C++ and Java. http://ws.apache.org/axis/ And in best traditions of Apache Foundation, it is FREE and OPENSOURCE. So, enjoy!
What is a “regular old fashioned web service?” An ASMX service, or are you using WSE as well? ASMX services are not naturally interoperable, don’t support WS-* specs, and ASMX is a technology that is aging very quickly. WSE (Web Service Enhancements) services DO add support for WS-* and can be made to be interoperable, … Read more
ASP.NET web services never fire Application_Error event and exceptions cannot be handled globally by ELMAH like in ASP.NET apps. But we can “manually” log exceptions using ELMAH: public int WebServiceMethod() { try { … } catch (Exception ex) { Elmah.ErrorLog.GetDefault( HttpContext.Current).Log(new Elmah.Error(ex, HttpContext.Current)); } }
You need to do this: List<ConsultantDto> myObjects = mapper.readValue(jsonInput, new TypeReference<List<ConsultantDto>>(){}); (From this SO answer) The reason you have to use TypeReference is because of an unfortunate quirk of Java. If Java had a proper generics, I bet your syntax would have worked.
CN=hostname – it’s the first option you’re being asked for here. It’s confusing that keytool refers to it as “first and last name”.
An HTTP POST doesn’t necessarily have to create a persisted resource. In RFC 2616, section 9.5 we find: The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either 200 (OK) or 204 (No Content) is the appropriate response status, depending on … Read more
WCF = Windows Communication Foundation A communication-oriented set of APIs and a “runtime” inside .NET to make two (or more) systems talk to one another. It basically replaces ASMX (ASP.NET web services), .NET remoting (object remoting) and a few other communication-related API’s and products in the .NET space. It can and should be used any … Read more