Skip to main content
java.oreilly.com -- Java and XML Tips and Tricks -- "SOAP or RPC?: For most inter- and intra-application communication, SOAP is overkill. Very rarely will you actually need the complex envelope handling, data mapping, and error processing in everyday Java-to-Java applications. Don't get me wrong--SOAP is great for communicating with non-Java components, UDDI registries, and through firewalls. It's just not the magic bullet that some are saying it is, and is a costly protocol in terms of overhead compared to simpler solutions like XML-RPC."

Gosh, I love O'Reilly! I've been struggling to differentiate SOAP & XML-RPC for corporate development teams and Brett McLaughlin's got just the piece I need!

Comments

Popular posts from this blog

On My Own - Doing It By The Numbers Over the weekend I got my first call on a consulting opportunity.  A few calls later I realized something - I hadn't figured out how to price my "product!" It's pretty hard for someone to buy something (or even determine whether they're interested) if they don't know the price. Of course, that realization came after I nailed down something even more important...my resume. I promised lots of friends, colleagues and former co-workers that I'd let them know how things are going, so I plan to catalog the steps in my process here on my blog in the unlikely event that someone else decides to pursue a similar path. I know this has probably all been written about before, but some of us are just too darned bull-headed to learn lessons from other people and need to make our own mistakes, carve our own paths. Step #1 - Define Your Product (aka Update Your Resume) I know most people probably keep their resumes current by looking at
InfoWorld published this excellent brief overview video on cloud computing. Worth a look if you're in the dark about the cloud!
GullFOSS - Sun Microsystems joins porting effort for OpenOffice.org for Mac We can only hope that there'll be some excellent cross-pollination between Sun's team and the folks at NeoOffice . NeoOffice has done a good job of delivering added value to OOo, and it would be a shame to see that good work fall by the wayside as the OOo core evolves to include its own Mac-native UX. I'm sure mine is not the only voice encouraging the teams to find ways to cooperate and bring the best of both to OpenOffice's Mac user community.