Comments for A New Day at the OfficeThis blog will provide an out-of-the-box approach to emerging technologies that the IT industry is dealing with every day. I will discuss technical topics from everyday events at the office. As a consultant I see new technologies daily and will discuss how those technologies are utilized, what's good, what's bad and what's just a buzz.Comment by Aleksandar Memca on Should we use SOAP for all communications- January 30, 2007 Depending on the JMS vendor that you have you may or may not have .NET APIs for Java. I know that it's an oxymoron to have JMS in .NET but it does exist. For example TIBCO's EMS product which is a TIBCO implementation of the JMS spec provides you C APIs for JMS. IBM has done something similar with MQ APIs.I've also seen native JMS calls from the .NET via a bridge or a .NET wrapper for JMS. The following post provides a good synopsis as well a href="http:blogs.msdn.comsmguestarchive2http://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/anewday/should-w... Comment by jmb on Should we use SOAP for all communications- January 30, 2007 Maybe I am missing something subtle, but how does introducing JMS further my cause. I am already stuck in a position where I am committed to a .Net front end and J2EE back end. Unless there is something fantastic that will bridge the tech stack, I can no more easily use JMS as I can RMI. So the problem remains the same. I'm open if there is something that I am missing, and not ashamed to admit it if there is. I am just not seeing it.http://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/anewday/should-w... Comment by Aleksandar Memca on Should we use SOAP for all communications- January 28, 2007 If I was in your position I would ask myself, what am I getting out of the SOAP stack That's what usually drives the decision because if you don't have a clear purpose then it's just an overhead. Granted, the overhead might be minimal in your environment but you can determine the percentage based on number of transactions, size of payload, parsing APIs that you use, etc. In my experience generating the automatic proxies usually ends in long hours making sure that the auto generated stuff frohttp://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/anewday/should-w... Comment by jmb on Should we use SOAP for all communications- January 24, 2007 I am still a bit confused about how to make a reasonable assessment for the use of SOAP. If I have a predefined architecture that mandates a .Net front end working with a J2EE middle tier, wouldn't I want to leverage SOAPWSDL to get all the automatic proxy generation and service routing stuff to help broker this communication. My team is currently in an active debate on this with the majority interested in using raw xml over http. My concern is that I see very quickly adding enough to bohttp://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/anewday/should-w... |