“Don Box is an architect assigned to the ‘Indigo’ project at Microsoft, where he is working on next-generation Web services protocols and plumbing. Box recently spoke with eWEEK Senior Editor Darryl K. Taft about upcoming technologies from the company such as the Language Integrated Query project, Windows Workflow Foundation and Windows Communication Foundation (Indigo).” In addition, here‘s an interview with Ray Ozzie, who Bill Gates is counting on when it comes to Internet services.
Who freakin’ cares? ;-p
Ahh yes, just what the world needs.
A propetiary answer to SOAP/AJAX.
Do people at Microsoft actually think this stuff sells???
Not to mention that they have been talking about it for more than 3 years now, and still have jack crap to show.
Please. Microsoft is such as has-been.
I don’t agree that MS has nothing to show as an alternative to Ajax. Check the new VS you might be surprised how far asp has gone though I couldn’t care less about it. On the other hand if you want to see how far JSP+Ajax sa gone there are quite some videos of the upcomming Sun Java Studio Creator 2. It is still an EA so there are a lot of bugs and probably some more features to be implemented. But the thing is amaizing and most of all it FREE. So yes I really don’t see what MS can bring to the table ( well other than locking down their server OS even more – if that’s even possible ). I guess it’s kind of hard to compeate with monopy though it is not impossile at all. Oh and Google kicks MS’s butt any day
Indigo builds off of SOAP (amongst other protocols; you’re free to pick the one you want, or even write your own) for it’s messaging system…so if you were to use something like MSMQ for the message transport, yeah it would be proprietary in that it could only talk w/ MSMQ, but the underlying message itself would still be SOAP, which is an open standard…and you do realize that Box co-authored the SOAP spec right?
I won’t even address the rest of your post as it’s absolutely ridiculous and not true.
all this soap/ajax is too much bloat. often xml is too much bloat.
imagine DNS or RADIUS done ia SOAP? yuk.
Why would you implement either of those w/ SOAP? Those are very poor candidates for what SOAP is actually used for…remote message delivery via an open protocol over HTTP (meaning no need to open up ports on your firewall other than 80).
That’s supposed to be a good thing? Allowing RPC to subvert firewalls by piggy-backing on top of HTTP just grates my nerves. Isn’t that the Microsoft mantra: why be safe when you can be convenient.
Apparently you’ve never heard of WSE then…and beyond that, it’s up to the receiving server of the SOAP message to decide what to do with it, there are plenty of security measures baked into SOAP (or whatever mechanism you decide to build to intercept the message).
It’s not just MS…SOAP is a widely used protocol by many vendors other than MS. It’s up to the programmer to implement security…the fact that it’s over HTTP is absolutely irrevelant in this case.
Seems to me that nowadays technology is becomnig all about complexity and new buzzwords and they are sticking XML in anywhere. Granted that technology is moving forward but at the same time I think a lot of people are getting disgusted by it. They need to clean all this layer on top of layer of crud. Set a standard and stick to it. Why do people follow MS standards all the time anyway?
Because the average programmer like nice gui based applications which allow them to use their mediocre VB skills and wow the CIO and the ignorant big wigs above him.
Lets hope that the Java Studio actually allows those with less than two brain cells to rub together, to enable them to get something up and working with minimum code and fuss.