Ignacio Silva-Lepe wrote:
I have been playing with the idea of a notification component
implementation
type that would serve as a vehicle to incorporate pub/sub interactions
into
SCA/Tuscany. Within a single composite or domain, producers and consumers
would be explicitly wired to and from a notification component (ie, a
component with an implementation.notification). In addition, to enable
produ-
cers and consumers to exchange messages across domains or even across
composites, a binding.notification could be used by composite references
and services.
I would like to create a couple of new modules in trunk to host code to
support
implementation.notification and binding.notification. If people are ok
with
it, I would
like to do this in the next few days.
Thoughts?
That sounds useful to me. I have a few questions:
Could you describe here how an application developer would program a
notification component? Will the component implement a fixed
notification interface or will this support user defined business
interfaces? Are notification methods just one-way methods?
What are you proposing for <implementation> and <binding> element? what
would they look like? How do you declare what you're going to publish
and how does a component declare a subscription? Do you have a sample
composite that you could paste here?
Are you thinking of flowing notifications over various protocols already
supported by Tuscany? or adding a new protocol through this new binding?
Thanks
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
