An early look at Windows Vista

[diabolus]

Most of what the 4Q1999 SOAP specifications did was simply illustrate how to model typed references and arrays in the W3C XML Schema type system. Period. We also had a model for adding optional and mandatory protocol headers (like CORBA's service contexts and DCOM's ORPCTHIS/THAT), but that was it. Frankly, had the schema specification been a full REC in 4Q1999, the SOAP specification would have at most 3-4 pages.

Does that answer anything?

 

[slimothy]

no

 

[pookfuzz]

I don't think it really matters who invented it; all I know is that almost every time I come across its use it is being used for the wrong reason.

For some reason SOAP seems to be one of those things the noob developers like using without there being a need. Then they sit and wonder why their apps are so slow.

 

[slimothy]

for some things its great, ever tried to dump the amazon product database?

 

[pookfuzz]

Nope, but then I would expect SOAP to be used for that sort of stuff.

The bad use I am talking about is people using SOAP to talk to the database on the other side of the room instead of ODBC or native drivers.

If the data is in a funny format or connecting to the DB directly is not an option then SOAP is great, in all other cases its nothing but a huge waste of performance.

 

[Roman4604]

Didn't LUX invent SOAP ... couldn't refuse that one.

 

[Perdition]

If you're calling Vista more powerful under the hood I think a raincheck might be in order. I haven't had time to read up on indigo, but Apple has had Aqua, most likely what avalon is a copy of, for ages ...

"Aqua" is just the name of the OS X GUI, this is equivalent to Longhorns "Aero" (a bit of a cheap shot on MS' part I admit). Avalon is the underlying graphics subsystem which would be equivalent to Tiger's Core Image and Core Video. Where Avalon shines is that it allows developers the ability to create visual applications that up until this point would have required a large amount of Direct X coding or specialised third part libraries.

Indigo is the new windows application messaging subsystem and alleviates many of the gripes developers have had with the current (and now quite dated) Windows messaging subsystem i.e. developers will will have a very robust communication platform on which to develop enterprise applications.

Basically Avalon and Indigo take much of the low level grunt work out of application development allowing developers to focus on adding features and value to their products. Even though Avalon and Indigo will be available for XP, they will be integrated directly into Vista, so at least for developers Vista provides a lot of value.

 

[malec]

Must have misunderstood that avalon description ...

 

[TheRoDent]

slimothy, just like you are incapable of inventing an original argument based upon some actual knowledge -- that, exactly, is how Microsoft didn't "invent" SOAP.

If someone invents a way of getting data from A to B, using XML encapsulation, and then, someone comes along later, and changes a couple of the tags used to encapsulate the payload. Would you call the latter an "invention"? Holy crap! NO! I would call it an EXTENTION, or perhaps, at a stretch, a new strain of the standard... But an invention? Never.

Microsoft didn't invent SOAP, or the basis of SOAP. They gave it a name, and submitted it to the W3C. Whoop de doo.

 

[Celemasiko]

Windows 3.1
Those were the days, no viruses and i was on fire with my 4meg ram!!!

hihi, I started with Windows 1.1. Before I had an Apple II with 46 KB of RAM. I was very proud after I could afford a 16 KB Memory Extension.*ggg*

 

[Byrd]

Hehe

I'll go you one better Celemasiko, I had a ZX80 (Older verison of the ZX81). It had 8k !!!! onboard with an optional 16k add on module. The worst of the whole lot was the terrible tapes that you would record your code with - they never worked

What - the ??? still awake @ 2 in the morning - get some sleep man