>> I've run into an issue here. In a previous version, someone was kind >> enough to work out the logistics of looking up information about a >> user and jam that in a vcard. So if I'm logged into PyICQ, I can >> look up vcard information about my test account. Well, here's the >> thing. Now there's avatars. This means the client will do a vcard >> request in order to retrieve the avatar. Well, that means I'm also >> asking for the directory type information when said avatar is >> requested. (same occurs with PyAIM as well actually, it's just less >> involved . . . AIM only has the Profile) So basically, asking for an >> avatar via vcard is an 'expensive' operation. I don't know what to >> do about this. I -could- cache the information received from the >> extended lookup, so at least i doesn't occur often. Of course, this >> means the info won't be up to date. Anyway, do any of you have any >> suggestions? Or do you think this is piddly enough of an 'expense' >> to not worry with it. It's typically a quick response, for what it's >> worth. As far as I know, there's no indication during a vcard-based >> avatar request that you are only really looking for the photo field. >> >> Daniel >> > > How about jep-0008? It is historical but so is vcard-temp based > avatars. > Though not many clients seem to support it, why is that? It doesn't > seem > that difficult to implement.
I do support that. =) (as well as vcard based avatars) But yeah, very little clients support it. I agree that it's easy I'm not sure why clients don't implement it. It's almost no different than vcards, save retrieving only what you want. =) Daniel > > /Jonas > > > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
