[JDEV] Re: [Win32-dev] Interface Ad Ins?

Tue Dec 21 11:31:45 CST 1999

Would it not be better to encapsulate the <ticker> and <symbol> in a <x> so 
that there NS could be defined per protocol ;-)

--temas

Thomas Charron [tcharron at ductape.net] wrote:
> Quoting Joe Osowski <awake at upallnite.com>:
> > Excuse if I'm going over old ground, but with all this talk about adding
> > different transports I had an idea.  Why not have the Jabber client be
> > plug-in based?  IE... a user gets a basic client with chat and whatever
> > support, but at later dates as more traports are developed, more tabs are
> > developed.  Stock Quotes, News, IRC, Server Alerts, Email... etc.  Users
> > can
> > pick and choose what they want their Jabber Client to do.
> 
>   Zabber actually already supports this type of functionality.  It has 
> a 'TicTacToe' example that allows two zabber users to play ticktactoe..  But 
> it's all plugin based.
> 
>   I know exactly what your talking about here, and the clients can actually 
> support 'both'.  Example would be the stock ticker:
> 
> <message to='you- from='ticker'>
> <subject>Your Personal Ticker</subject>
> <body>
> RHAT: 219
> LNIX: 245
> OXHP: 12
> </body>
> <ticker xmlns='jabber::ticker'>
> <symbol name='RHAT'>219</symbol>
> <symbol name='LNIX'>245</symbol>
> <symbol name='OXHP'>12</symbol>
> </ticker>
> </message>
> 
>   In this example, 'standard' clients will recieve the message and be able to 
> read it, but clients that are 'extentions aware' can detect foreign namespaces 
> within a message, and pass the message off to a plugin who has those external 
> namespaces registered.
> 
>   Essentially, this support 'dumb' clients, as well as smarter ones who may 
> display this data differently then standard messages..
> 
> --- 
> Thomas Charron
> << Wanted: One decent sig >>
> << Preferably litle used  >>
> << and stored in garage.  ?>>
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/19991221/3ace407f/attachment-0002.pgp>