Slashdot Mirror
San Mehat On Web Services & .Net
A reader writes: "There's an interview with San Mehat in regards to .Net & Webservices. He has some interesting comments about what will work and what won't work, and where things are going." San is well known for his Netwinder work, as well as being a good DJ. And, in the interest of full disclosure, San does work for VA Software, the parent company of OSDN, as is DevChannel.
Mono is an open source implementation of .Net Development Framework.
You can find it here
This is RiverTonic's sig.
Every time I build it's basically 50/50 whether or not the compiler is going to start throwing spurrious exceptions.
You must have a corrupt install. I've been working professionally with VB.Net for about 2 years now and have never had a compile go bad, except when it was my fault.
The rest of the IDE, on the other hand, is about as stable as a crack ho. My favorite is when it opens up project files for me automatically and randomly, just because it decided to. Source safe integration is also a joke.
SOAP has several parts and he seems to be confusing them. Most all of the major vendors are using Schema (another W3 standard) for types and SOAP for enveloping but not encoding.
.Net does not use it by default but rather uses SOAP enveloping with Literal encoding.
SOAP encoding is recognized as incompatible and limiting which is why
While Mr. Mehat states this as a criticism, I going to come out saying that this is a strength. SOAP is very light weight considering its alternatives. In-so-far as you can serialize objects to W3C Schema primitive types, you can avoid the difficulties of complex marshaling one incurs with other distribute service mechanisms (the stubs/skeletons of CORBA, etc.). The W3C Schema types are a quick and easy standard that are independent of choice of language, operating system, environment, etc.
I put the 'fun' in fundamentalism
why does his DJ description read like marketing-speak?
;)
San's years of DJing experience playing parties and clubs from California to Canada have put him close in touch with the dancefloor and its needs.
my favorite thing he says is "SOAP allows you to do a lot, but also gives you just enough rope to hang yourself." must be soap on a rope.
No offense why are you working with vb.net?
Don't underestimate the power of the dark side. Put another way, when the suits say the whole team will use VB.Net, and when you are not independently wealthy, that's what you use.
Anyways, after using various incarnations of VB for about 7 years, I don't really mind it anymore. I started as a C++ programmer and thought VB was crap. These days, don't care. Quality of source code depends much more on the quality of the programmer than on the quality of the language. It's the man, not the machine I guess.
And also... My fellow Java developer and myself have had zero problems exchanging complex types over web services. There is no problem with XML/SOAP. The problem lies in immature proxy generators. WebSphere Studio Application Developer and the
in my experience... if you wanna pass more complex datastructures over webservices, you send objects encoded as xml strings... then decode the xml into the native structures you want.
.NET services already in place. the hardest stuff i've had to tackle in the interoperability between java and .NET is getting into the soap headers... and then just getting commonality between encryption classes etc. lot's of hurdles and non-overlapping block styles and things. drive me crazy!
sure, it's work, but so it goes.
that's how we've gotten around a lack of standardization of higher level objects.
i've been writing a set of java services to serve as a linux option to some
gosh, and then how some of those wsdl and stub generator tools in java land have changed and produce different code. shoot me now!
m.