RE: [PHP-DEV] SOAP and BizTalk

On Wed, 7 Jun 2000, Fredrik Larsson wrote: > >> - SOAP is definately slower than any other method e g EJB and Corba. But > >> speed is becoming a less problem as we continue to grow older... > > > >Thats a very Microsoft way of looking at things. The cpu's fast enough, so > >we can be sloppy. > > Yes it is. But don't forget who is paying our bills. What do your think your > customer rather would pay for? $1000 for a fast device or $10000 for your > consulting hours? Do remember that we are expensive. Hardware is cheap... Speed of development and speed of running are different things. I was talking about speed of running. Now if you are woried about development times, just use visual basic for everything. Its fast to develop, its memory intensive, its slow as hell, but its cheep to develop for. ;) I as a C coder can churn out C code faster then most VB coders can churn out VB code. Teach the coders to code and developer costs will go way down. Doing it right doesnt nessisarily cost more. (usually, in the long run, it costs LESS) > > >I do not see SOAP being more flexable then CORBA. > > Don't CORBA require a dedicated ORB? > Doesnt SOAP require something like an ORB? The technologies are very similar, I'm sure it has an equivilent. > >CORBA has allowed windows, dos, unix, macos, whatever to communicate for > >along time. SOAP is new to that. And, taken all previous actions of MS > >into account, they have allways taken a stance of INcompatability, not > >compatability. Ask yourself why then is MS suddenly pushing a "compatable" > >protocol. > > Microsoft isn't alone on this one. Sun, IBM and more a behind this. The SOAP > mailinglist is supposed to have about 1000 developers in it. Not all of them > are MS-fans. But they are there to make a difference and they do. If I am > correct the SOAP specification is proposed as a standard (IETF I think) and > that means a bit out of MS hands. It's clear that you like CORBA very much > and for very good reasons to. The more tools we have at our hands the more > important it is. I am a fan of standards. I just get really... upset when a new "standard" is created when a perfectly good one already exists. It makes things incompatable and CORBA/SOAP were designed primarily for promoting object compatability. Having 2 standards destroys what they both exist for in the first place. > > >> - Will SOAP be successful? Well, what are the most common used ORB in the > >> world? Apache and IIS last time I checked... > > > >HAHAHAHA. Apache and IIS are NOT ORBs. > > They aren't? Well... I create a PHP script that has an object that calculate > something. My client application then call the webserver and request the > result of the calculation. Doesn't that make the webserver (Apache and IIS) > the ORB? An ORB is a CORBA term. it refers to the code that allows communication between an object and its client. in your senerio, the object would have to be a corba one, php would be the language the object was written in, an orb would be nessisary, and apache could be used as a communication protocol. apache would not be an orb, its a web server. ORB=Object Request Broker. > > Anyway the orginal point for this thread was about SOAP support in PHP and I > personally vote for it since I like them both. > If someone wants to implement it, thats fine, but I beleave its against the principle of why SOAP and CORBA exist in the first place. It will furter degrade interoperability between objects.