Early next week, I'll send out the first issue of my free "Distributed .NET Newsletter".
This bi-weekly newsletter contains real world tips and tricks about .NET Remoting, Web Services and EnterpriseServices, and design guidance for distributed applications. You'll also find the occasional pointers to other free resources like white papers, patterns&practices documents or other great samples on the web.
You can subscribe to the newsletter in HTML or plaintext format at http://www.ingorammer.com/contact/Newsletter.aspx.
[Ingo Rammer's DotNetCentric]
Ingo definitely knows his .NET Remoting. Check it out, no strings attached.
In today's devx newsletter, in an article-short entitled "Convert Code from VB.NET to C#", Marco Bellinaso identifies a couple of available services for converting C# code to VB. He says, however, that he is unaware of any tools that perform the reverse translation (from VB to C#), and then goes on to describe a workaround process for doing this that uses Anakrino.
A couple of months ago, someone (I think it was Chris Sells) pointed me to an open source utility called BabbelFisken that does exactly this. In fact, BabbelFisken also converts from Classic VB to C#, from Delphi to C#, and from Turbo Pascal 5 to C#!
Source code (C#) included. Check it out.
I thought I'd come out more bohemian, but probably so much time spent on XP has made me one of its own! (Thanks to Sam Gentile for the link)
Which OS are You?
TimBL nails it, IMO (emphasis mine):
San Francisco Chronicle is reporting on TimBL's speech to NSF...Tim made the point that "web services" are about performing remote operations. When viewed in high contrast, "web services" build a web of interconnected verbs, while "semantic web" builds a web of interconnected nouns. It was encouraging to see a journalist relaying the message that the two worlds will be complimentary, rather than succumb to the typical Zoroastrian storyline. [Better Living Through Software]
This metaphor seems to be a very nice model to keep in mind when you are architecting your services, and going crazy trying to reconcile the SOAP-centric and REST-centric perspectives. It's just verbs and nouns.
I'm no REST guru, but I think the RESTians would say you already have the 3 or 4 verbs you need in the HTTP protocol. This just isn't sufficient (even if expressible, it's not very accessible)for complex LOB enterprise applications. They may all eventually boil down to the 4 CRUD actions, but you need to supply a richer verb set, a domain-centric verb set.
Of course others have already provided very practical advice on designing RESTful SOAP.