[OpenAjaxInterop] Howard's changes to Hub 1.1 proposal page

Howard Weingram weingram at tibco.com
Wed Dec 10 18:35:26 PST 2008


Thanks, Jon.

Regards,
Howard 


On 12/10/08 4:57 PM, "Jon Ferraiolo" <jferrai at us.ibm.com> wrote:

> OK, thanks. Yes, it makes sense to leave getParameters() on OpenAjax.hub.Hub.
> 
> Jon
> 
> 
> Howard Weingram <weingram at tibco.com>
> 
> 
>>>>> Howard Weingram <weingram at tibco.com>
>>>>> Sent by: interop-bounces at openajax.org 12/08/2008 11:10 PM
> 
> To 
> 
> Javier H Pedemonte/Austin/IBM at IBMUS, <interop at openajax.org>
> 
> cc 
> 
> 
> Subject 
> 
> Re: [OpenAjaxInterop] Howard's changes to Hub 1.1 proposal page
> 
> See below.
> hw
> 
> On 12/8/08 1:26 PM, "Javier H Pedemonte" <pedemont at us.ibm.com> wrote:
> 
>> > Howard Weingram <weingram at tibco.com> wrote on 12/05/2008 03:52:35 PM:
>> > 
>>>>> >>>> 3. getParameters()
>> > 
>> > During the call today, Jon brought up the point that the getParameters()
>> > function is on the Hub interface, which means it is a method on both the
>> > ManagedHub and HubClient impls (it is also a function on the Container base
>> > object).  But you only described it being used as a function on ManagedHub.
>> > Should we only have this function on ManagedHub?
> 
> HubClient constructors must also take a params object, and
> HubClient.getParams() allows client code to retrieve this in a standard
> manner, as with ManagedHub.getParams().
> 
> So I have a slight preference for leaving this function on the common Hub
> interface. 
> 
>> > 
>>> >> 5a. Regarding one or two onError functions:
>>> >> 
>>> >> Currently, I have been using 2 different functions:
>>> >> 
>>> >>  * onSecurityAlertError
>>> >>  * onWarning
>>> >> 
>>> >> The onWarning function handles asynchronous errors that do not appear to
be
>>> >> dangerous, while the onSecurityAlertError reports suspected attacks. My
>>> >> thinking is that we need an easy way to distinguish suspected attacks >>>
from
>>> >> less urgent issues. I avoided forcing the triage mechanism to depend on
>>> >> exhaustive enumeration of specific errors, because different
>>> >> Container/HubClient implementations may have specialized errors/warnings.
>>> >> Generic application code may not recognize every type of error/warning
>>> >> generated by every type of Container. Treating every warning as a
>>> suspected
>>> >> attack would probably be overkill. Treating a suspected attack as a
>>> warning
>>> >> could be a big mistake. I could have had some kind of severity flag, I
>>> >> suppose, but I figured that a manager's behavior when an attack is
>>> suspected
>>> >> (we probably destroy the container immediately) is much more extreme than
>>> >> the behavior when a "warning" is received. Thus, I separated the two
>>> >> handlers. Since many applications might not care about warnings at all, 2
>>> >> functions seemed easiest and most efficient. However, a severity flag is
>>> >> another possible option.
>> > 
>> > This seems fine to me.  And I prefer the 2 functions rather than a security
>> > flag. 
> 
> Cool.
> 
>> > 
>>> >> 5b. Tangent: viewing permission-denied as warning vs. as attack
>>> >> 
>>> >> Right now I am treating authorization failures (onPublish returns false)
as
>>> >> warnings rather than as attempted attacks. I don't know whether everyone
>>> >> else agrees with this approach.
>>> >> 
>>> >> 5c. Regarding why we should tell the client when publish fails (good
>>> >> question): 
>> > 
>> > I'm fine with both of these.
> 
> Cool.
> 
>> > 
>> > 
>> > Javier H Pedemonte
>> > 
>> > 
>> > 
>> > 
>> > _______________________________________________
>> > interop mailing list
>> > interop at openajax.org
>> > http://openajax.org/mailman/listinfo/interop
> 
> 
> 
> --
> 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
> 
> _______________________________________________
> interop mailing list
> interop at openajax.org
> http://openajax.org/mailman/listinfo/interop
> 
> 
> 
> 
> 
> --
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openajax.org/pipermail/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/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/interop/attachments/20081210/48996936/attachment-0008.gif 


More information about the interop mailing list