Mercurial > pidgin.yaz

comparison libfaim/README.gaim @ 503:6e318907bcce

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[gaim-migrate @ 513] bringing gaim up to latest libfaim committer: Tailor Script <tailor@pidgin.im>
author Eric Warmenhoven <eric@warmenhoven.org>
date Tue, 18 Jul 2000 05:37:39 +0000
parents 22700acd9b49
children 926ba0807a2d
comparison
equal deleted inserted replaced
502:4d1e39112cbd 503:6e318907bcce
58 Warning users/getting warned 58 Warning users/getting warned
59 Chat: 59 Chat:
60 - whispering (this will never happen) 60 - whispering (this will never happen)
61 Getting/setting dir info 61 Getting/setting dir info
62 Changing your password 62 Changing your password
63 File transfer/IM images/voice chat/etc. 63 File transfer/IM images/voice chat/etc. (RVOUS stuff)
64 64
65 KNOWN ISSUES 65 KNOWN ISSUES
66 ============ 66 ============
67 - Oscar doesn't do whispering in chat rooms any more (and hasn't for quite a 67 - Oscar doesn't do whispering in chat rooms any more (and hasn't for quite a
68 while, evidently). So if you want to "whisper" to someone, just IM them. 68 while, evidently). So if you want to "whisper" to someone, just IM them.
85 85
86 - If you receive a message that's too large, gaim segfaults. I haven't watched 86 - If you receive a message that's too large, gaim segfaults. I haven't watched
87 this in gdb or gotten a backtrace on it, so I'm not exactly sure what the 87 this in gdb or gotten a backtrace on it, so I'm not exactly sure what the
88 problem is. I think this actually happens on the TOC side of things too. 88 problem is. I think this actually happens on the TOC side of things too.
89 89
90 - Gaim/TOC can do file transfers, but Gaim/Faim cannot. This is not because 90 - Gaim/TOC can do RVOUS actions, but Gaim/Faim cannot. This is not because
91 there is any difference in the two protocols as far as the actual transfer is 91 there is any difference in the two protocols as far as the actual transfer is
92 concerned. The only thing preventing this is it is currently not possible to 92 concerned. Adam wants libfaim to handle *all* of the RVOUS connection stuff,
93 recognize when we've received a file transfer request using libfaim. Once 93 which I can understand. Unfortunately, the only part he's implemented is Direct
94 libfaim can tell us that we've received the request, the only thing we should 94 Direct IM, and I haven't implemented that on the gaim side yet.
95 need to change is to have oscar.c wait for one of those notifications and then
96 call accept_file_transfer() from rvous.c. No modification of rvous.c should be
97 necessary at that point. (The same should apply to IM Images and Voice Chat and
98 all the other RVOUS stuff - they are all protocol-independent.)
99 95
100 - What *is* protocol-dependent about the RVOUS stuff is that only Oscar can 96 - What *is* protocol-dependent about the RVOUS stuff is that only Oscar can
101 request RVOUS actions, though both can receive them. However, libfaim cannot 97 request RVOUS actions, though both can receive them. However, libfaim cannot
102 yet make the requests, so there is no difference between Gaim/TOC and Gaim/Faim 98 yet make the requests, so there is no difference between Gaim/TOC and Gaim/Faim
103 there. 99 there.