Geoff,

> My initial look at the services API implies (to me)
> that there is enough overlap if property requirements to make it so
> that a single component is appropriate. The set of properties are
> assigned to the component, and appropriate functions called to
> initiate the service desired.

there are at least two kinds of services that work quite differently
from each other; the IBX implementation in this regard is not something
that I like much, but the object hierarchy used is quite clever.

> With this shared
> functionality and common interface requirements, it seems to make
> sense to present it in a single component.

...or a properly factored-out class hierarchy.
I could be wrong too, though. ;-)
Bye
--
____
_/\/ando