symptom: program crashes, or continues working but with wrong data
maybe yours, but if the IDL differs you should get marshalling exceptions.
And don't start about interface inheritance - it's a nightmare to use for more than a single addition (image 5 ot 6 additions over the course of a few months)
you should prefer composition over inheritance anytime. Deep inheritance hierarchies usually signal bad design.
Just say 'no' to CORBA.
I say just say 'no' to speaking without thinking.
CORBA may not be the right tool for the types of tasks that SOAP tries to resolve; SOAP may not be the right tool for some tasks where CORBA shines.
The two overlap in their capabilities and each has strengths and weaknesses. I guess it's up to the discerning architect to decide what should be used. Sadly enough, people with decision power today are too buzzword-driven to be discerning.
Slashdot Mirror
wow, I never knew it was all so simple.
symptom: program crashes, or continues working but with wrong data
maybe yours, but if the IDL differs you should get marshalling exceptions.
And don't start about interface inheritance - it's a nightmare to use for more than a single addition (image 5 ot 6 additions over the course of a few months)
you should prefer composition over inheritance anytime. Deep inheritance hierarchies usually signal bad design.
Just say 'no' to CORBA.
I say just say 'no' to speaking without thinking.
CORBA may not be the right tool for the types of tasks that SOAP tries to resolve; SOAP may not be the right tool for some tasks where CORBA shines.
The two overlap in their capabilities and each has strengths and weaknesses. I guess it's up to the discerning architect to decide what should be used. Sadly enough, people with decision power today are too buzzword-driven to be discerning.
assert() failed - does that mean Sony ships debug code (-DNDEBUG not there?)