[OpenAjaxGadgets] Remove <property topic="">

Wed Apr 15 14:01:29 PDT 2009

It needs to always be up to the policy of the canvas whether a particular 
property is shared or not (security, wiring and the like might all come 
into play). As soon as you accept that then not implementing property 
sharing at all is simply a particular policy enforcement ....

Rich 

From:
Jon Ferraiolo/Menlo Park/IBM at IBMUS
To:
Howard Weingram <weingram at tibco.com>
Cc:
"gadgets at openajax.org" <gadgets at openajax.org>
Date:
04/14/2009 12:46 PM
Subject:
Re: [OpenAjaxGadgets] Remove <property topic="">

I'm fine with removing the 'topic' attribute from the PROPERTY element.

But why MAY instead of SHOULD? What are the reasons that the property 
management system wouldn't send notifications? 
* Are you thinking that some host software environments won't implement 
shared properties, and this is OK?
* Are you thinking that some host software environments will implement 
shared properties, but will have security systems that will restrict which 
properties are shared?

I'm asking this because we might want to include informative text that 
provides some explanation about various scenarios where property values 
might be shared or might not be shared.

Jon

Howard Weingram <weingram at tibco.com>

Howard Weingram <weingram at tibco.com> 
Sent by: gadgets-bounces at openajax.org 
04/11/2009 06:03 PM

To

"gadgets at openajax.org" <gadgets at openajax.org>

cc

Subject

[OpenAjaxGadgets] Remove <property topic="">

Hello, folks.

Having seriously thought about some of the comments last week, I would 
like
to propose a simplification of the <property> pubsub behavior along the
lines briefly suggested last week.

Allow <property> to have the following pubsub attributes, with the 
following
specified meanings:

1. Attribute: publish="<Boolean>"

If the publish attribute is present and true, then when the property
management system sees a change in the value of this property, it MAY 
notify
other widgets (not just this widget) of the change.

2. Attribute: subscribe="<Boolean>"

If the subscribe attribute is present and true, then when the property
management system detects a change in the value of this property, it MAY
notify this widget by calling the widget's onChange function.

3. Attribute: topic="<String>"

Get rid of the topic attribute.

Rationale:

Widgets must ONLY use the specified property functions
(Adapter.setPropertyValue, Adapter.getPropertyValue, Widget.onChange,
Widget.onChange<Property>) to access the property values.

The implementations of these functions, including ALL event delivery
functionality:

* are simply implementation details of the host,
* are completely hidden from the widget, and
* should not be controlled by widget.xml at all.

This includes:

* Whether the Hub is used, vs. some toolkit's existing
   property management or notification system
* If the Hub is used, what Hub topic/s are used
   (Why does the widget care? It's dealing with properties here)
* Whether the mash-up/tool enforces security policies that prevent access
   to certain properties or topics
* Whether the mash-up/tool provides features that allow end-users to wire
   widgets together manually

Any mash-up or mash-up framework that uses the Hub for event notification 
at
run-time must somehow (either automatically or by asking the developer for
input) provide topics for delivery of these events. The exact topics used
should not be under the control of widget.xml, which has no idea how a 
given
mash-up framework works or what kinds of topics it finds convenient to 
use.

Property update events (as opposed to events that the widgets publish
explicitly using hub.publish) are always implementation details of the
framework or mash-up.

This reduces the complexity of the OAWM spec, albeit slightly, and allows
application/framework developers the freedom to do what works best for 
them.

BEST PRACTICE for mash-up and framework implementers:

For that use events to communicate any information, including property
updates, use topic names that use reverse package notation starting with
your organization name, e.g. "com.tibco.my.foo.bar" so as to avoid
collisions between your events and those of other vendors and developers.

Regards,
Howard 

--
Howard Weingram      650.846.1000
Principal Architect  TIBCO Software Inc.

TIBCO PageBus(TM) delivers ultra-lightweight
publish-subscribe messaging for mash-ups.
Learn more at http://www.pagebus.org

_______________________________________________
gadgets mailing list
gadgets at openajax.org
http://openajax.org/mailman/listinfo/gadgets
[attachment "pic02458.gif" deleted by Rich Thompson/Watson/IBM] 
_______________________________________________
gadgets mailing list
gadgets at openajax.org
http://openajax.org/mailman/listinfo/gadgets

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment-0001.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment-0002.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment-0003.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment-0004.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment-0005.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment-0006.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment-0007.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://openajax.org/pipermail/gadgets/attachments/20090415/ee042404/attachment-0008.gif 