[Gossip-dev] [PRE-PATCH] feature cache

Julien PUYDT julien.puydt at laposte.net
Thu Dec 30 20:06:47 CET 2004


Hi,

to have a working disco, gossip will need two things:
* when the other end says it has feature 'foo2', be able to find in a
cache that it means features 'jabber:x:foo' and 'jabber:x:foo2' are
available (or ask what it means and put the answer in said cache);
* when gossip tells it has feature 'foo2', be able to answer the other
end if it asks what it means.

I think the best is to have a feature cache, that would be a singleton
object associated to the jabber protocol, and get seeded both by:
* gossip itself: when an extended feature is supported, its name and the
list of corresponding feature should be put in there ;
* external sources: when gossip has to ask about a feature to someone,
it should store the answer (see last paragraph of 4.2 in JEP0115).

The following pre-patch has very basic caching capabilities, but gives a
basis for discussion (it doesn't really save&reload what it cached, it
takes any information as 100% sure [bad for security]). It mostly served
me to make some tests with the feature bundle manager pre-patch.

Still, if it can be of some use...

Snark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gossip-jabber-feature-cache.patch
Type: text/x-patch
Size: 6996 bytes
Desc: not available
Url : http://lists.imendio.com/pipermail/gossip-dev/attachments/20041230/f998fc73/gossip-jabber-feature-cache.bin


More information about the Gossip-dev mailing list