[Xpipe-developers] XPipes, Generational Programming, and binding

[David S. <ds...@st...>]

A few more questions as I continue to try and wrap myself around the XPipe
way of thinking.  To me, the value of a pipeline/component based system is
the ability to build a variety of reusable domain specific components in
addition to the general purpose components that will undoubtedly be
developed.

The thing one frequently wonders about these systems is how tight or loose
and how static our dynamic the bindings are.  XComponents are loosely bound.
What is envisioned about how static/dynamic the bindings are?  If an XPipe
description, like an XComponent description, is an XML file can I create one
during execution and then use it?  Would I want to given the way the
architecture is currently envisioned?  Likewise, could I generate an XSLT
and an XComponent description for it, bind it to other XComponents at
runtime and execute it all?

Am I asking reasonable questions, or just being crazy as usual?

David

David Starr
18 Winthrop Terrace
Wayland, MA  01778
(508) 358-2975
da...@st...