Re: Why do we have a component model?

Hi Paul,

> seems to me that we spend most of our time trying to fix bugs in the
component
> model, in particular the area of composition.

Can you back that up with real info please? I'd be impressed if you could
indeed
show that we spend most of our time on component model problems. IIRC
very few of our LC comments are about the component model *per se*; of
course they have component model implications as that's how WSDL is
defined.

If you want to claim that the Z notation stuff has brought up lots of
problems,
well, then the problem is that we decided to retrofit an abstraction on top
of
an abstraction.. not the other way around. Record will show that I was
against
doing the Z notation from day one.

>The engineer in me wants to find a
> simpler solution rather than continue to add more sticky tape and chewing
gum.

Well so do I. I hardly find this particular assault on the component model a
good reason to throw it all away and start with a new mess.

As was re-asserted at the F2F, the spec as its written was explicitely not
written for end-users (read as people implementing services) but rather for
implementors (read as people implementing WSDL tools/runtimes, SOAP
stacks, etc.). The component model provides a degree of rigour to that; so
read with the runtime and tooling engineer in you rather than the Web
service
author engineer in you. I know you have at least two engineers in you! ;-)

> i'm drawn to the idea of spec which is focused on the document rather than
the
> processing model, even if that meant losing import (but keeping a lexical
include).

Been there, done that. Again, with all due respect, you need to read the
archives and see how we got here. I personally was against adding import/
include but lost. Such is the world of design by committee; somethings you
like, some that you don't. The other option is design in a closed room;
would
you prefer that (esp. if you didn't happen to be in the room)?

Sanjiva.

Received on Tuesday, 8 March 2005 15:26:48 UTC