[Standards] Jingle "implementability"

[Robert Quattlebaum]

On Feb 1, 2008, at 1:14 AM, Maciek Niedzielski wrote:

> Robert Quattlebaum pisze:
>> On Jan 31, 2008, at 1:10 AM, Michal 'vorner' Vaner wrote:
>>> Why couldn't it know now? If you are unable to filter/register by  
>>> other
>>> criteries than just the namespace of toplevel child, then you will  
>>> find
>>> problems elsewhere, too.
>> If the app-level stanza router was stateful (ie: keeping track of  
>> which session ID's were associated with each jingle app type), then  
>> yes, it could know. However, there appears to be no way to do this  
>> in a stateless fashion.
> Stanza router could pipeline jingle stanzas through all jingle  
> plugins. Since a plugin tracks state, etc, it knows if it is  
> interested in this stanza or not. So if it wants the stanza, stanza  
> gets "eaten", else app-level stanza router tries to pass it to next  
> plugin, etc.

While such a model works well for apps with plug-ins in the same  
process as the app, it does not work as well if your plug-ins are in  
different processes--because it would be a blocking API.

__________________
Robert Quattlebaum
Jabber: darco at deepdarc.com
eMail:  darco at deepdarc.com
www:    http://www.deepdarc.com/



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.jabber.org/pipermail/standards/attachments/20080201/311ae6b3/attachment.htm