[Telepathy] some questions for telepathy spec
Hi, All, I am rather new to the telepathy project, and I feel this project could be a very good framework for my development. However, after I read the spec of telepathy http://telepathy.freedesktop.org/spec.html , I have few questions: 1. Via the methods of org.freedesktop.Telepathy.Channel.Type.Text interface, client can send and receive text message with contact. But how can I identify the encode of the messages? should I read this encode information from the channel properties? 2. As we know, some protocol (SIP/SIMPLE) provides a feature that the text chatting (send / receive text message) happens in a session. Under telepathy framework, how the session can be identified ? Or currently, telepathy can not support this feature ? -- Regards！ Liangjing ___ Telepathy mailing list Telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] some questions for telepathy spec
Hi, From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Liangjing Zhao Sent: Monday, August 20, 2007 9:35 AM To: telepathy@lists.freedesktop.org Subject: [Telepathy] some questions for telepathy spec However, after I read the spec of telepathy http://telepathy.freedesktop.org/spec.html , I have few questions: 1. Via the methods of org.freedesktop.Telepathy.Channel.Type.Text interface, client can send and receive text message with contact. But how can I identify the encode of the messages? should I read this encode information from the channel properties? On the Telepathy side, message text and other user-readable data are considered plain text in UTF-8. 2. As we know, some protocol (SIP/SIMPLE) provides a feature that the text chatting (send / receive text message) happens in a session. Under telepathy framework, how the session can be identified ? Or currently, telepathy can not support this feature ? A chat session is represented by a channel object implementing org.freedesktop.Telepathy.Channel.Type.Text. Best regards, Mikhail ___ Telepathy mailing list Telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
[Telepathy] [Bug 12066] New: Crash while starting a voip call
http://bugs.freedesktop.org/show_bug.cgi?id=12066 Summary: Crash while starting a voip call Product: Telepathy Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: stream-engine AssignedTo: telepathy@lists.freedesktop.org ReportedBy: [EMAIL PROTECTED] The crash is 100% reprodubicle while using ereseva to call an n800. I got this trace by doing thread apply all bt full: Thread 8 (Thread -1265005680 (LWP 29778)): #0 0xe410 in ?? () No symbol table info available. #1 0xb4998298 in ?? () No symbol table info available. #2 0x in ?? () No symbol table info available. #3 0x0002 in ?? () No symbol table info available. #4 0xb7a195e7 in poll () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #5 0xb7768b96 in task_monitor_alsa (data=0x81fd308) at gstalsamixer.c:405 rnfds = 1 revents = 0 __PRETTY_FUNCTION__ = task_monitor_alsa #6 0xb7e8ea46 in gst_task_func (task=0x8215408, tclass=0x8215248) at gsttask.c:192 t = -1209472581 lock = (GStaticRecMutex *) 0x81fd398 tself = (GThread *) 0x81f9600 __PRETTY_FUNCTION__ = gst_task_func #7 0xb7b073f8 in ?? () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #8 0x08215408 in ?? () No symbol table info available. #9 0x08215248 in ?? () No symbol table info available. #10 0xb7aa1541 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 No symbol table info available. #11 0xb7b058df in ?? () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #12 0x082152d8 in ?? () No symbol table info available. #13 0x081f9600 in ?? () No symbol table info available. #14 0x in ?? () No symbol table info available. Thread 7 (Thread -1256612976 (LWP 29777)): #0 0xe410 in ?? () No symbol table info available. #1 0xb5199158 in ?? () No symbol table info available. #2 0x in ?? () No symbol table info available. #3 0x0001 in ?? () No symbol table info available. #4 0xb7a195e7 in poll () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #5 0xb76aad94 in snd_pcm_wait_nocheck () from /usr/lib/libasound.so.2 No symbol table info available. #6 0xb76aaf7f in snd_pcm_wait () from /usr/lib/libasound.so.2 ---Type return to continue, or q return to quit--- No symbol table info available. #7 0xb76ab0b8 in snd_pcm_read_areas () from /usr/lib/libasound.so.2 No symbol table info available. #8 0xb76b73ec in snd_pcm_mmap_readi () from /usr/lib/libasound.so.2 No symbol table info available. #9 0xb76a50b5 in snd_pcm_readi () from /usr/lib/libasound.so.2 No symbol table info available. #10 0xb776f10f in gst_alsasrc_read (asrc=0x814, data=0x822edc0, length=340) at gstalsasrc.c:766 alsa = (GstAlsaSrc *) 0x814 cptr = 170 ptr = (gint16 *) 0x822edc0 __PRETTY_FUNCTION__ = gst_alsasrc_read #11 0xb7750d33 in audioringbuffer_thread_func (buf=0x8144248) at gstaudiosrc.c:222 read = 136506816 left = 340 len = 340 readptr = (guint8 *) 0x822edc0 ��\002 readseg = 2 src = (GstAudioSrc *) 0x814 abuf = (GstAudioRingBuffer *) 0x8144248 readfunc = (ReadFunc) 0xb776f060 gst_alsasrc_read __PRETTY_FUNCTION__ = audioringbuffer_thread_func #12 0xb7b058df in ?? () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #13 0x08144248 in ?? () No symbol table info available. #14 0x0821d260 in ?? () No symbol table info available. #15 0x in ?? () No symbol table info available. Thread 6 (Thread -1248220272 (LWP 29776)): #0 0xe410 in ?? () No symbol table info available. #1 0xb599a228 in ?? () No symbol table info available. #2 0x0001 in ?? () No symbol table info available. #3 0x in ?? () No symbol table info available. Thread 5 (Thread -1239827568 (LWP 29775)): #0 0xb7aead2b in g_logv () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #1 0xb7aeafa9 in g_log () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #2 0xb7aeb08b in g_return_if_fail_warning () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #3 0xb7b9f476 in g_value_get_pointer () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #4 0xb7b866d4 in g_cclosure_marshal_VOID__UINT_POINTER () ---Type return to continue, or q return to quit--- from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #5 0xb7b787b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #6 0xb7b8a725 in ?? () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #7 0x08129398 in ?? () No symbol table info available. #8 0x in ?? () No symbol table info available. Thread 4 (Thread -1230828656 (LWP 29774)): #0 0xe410 in ?? () No symbol table
Re: [Telepathy] Proposed standard MC API
On Friday 10 August 2007 20:08:14 Xavier Claessens wrote: 1) They have translated fields The current profiles implementation do, but do we really need them? Are things like the description, display name etc really necessary for the profile? Can we move these out somehow? 2) Clients wants to select blessed CM that works for them. A client without MUC won't install tp-idle profile, clients don't want to support officially the last very unstable CM that will break everything. Isn't the whole point of profiles to abstract away any CM's particular features and thus stop a client from having blessed CMs? 3) There is UI related information, like which UI plugin to use to display the protocol-specific setting widget. This shouldn't be in the profile imho. 4) Some defaut values for CM depends on policies, like should we ignore-ssl-errors which is a security flaw but (atm) required to connect GTalk. I propose we simply have a supports-secure-connection capability and let the client decide on policy (and inform the user etc). GetConnectManagerName()- s GetProtocolName()- s GetDisplayName()- s -- Translated string GetDescription() - -- Translated string GetIconName() - s -- Following the fd.o icon-naming spec. GetCapabilities - as possible capabilities copied from NMC: chat-p2p chat-room chat-room-list voice-p2p contact-search split-account registration-ui supports-avatars supports-alias supports-roster GetSupportedPresences() - au GetVCardField() - s IsDefaultVCard() - b I have no idea what the split-account and contact-search capabilities mean. So far I've decided to use the following capabilities (incomplete): supports-encrypted chat-room chat-p2p voice-p2p registration-ui Avatars can be determined by looking at which interfaces the CM exports. Is it really necessary to have this in the capabilities? Can anyone think of any additional capabilities which should be added? Maybe we can specify a file format to store profiles and MC should then look for all xdg dirs/share/mission-control/*.profile I agree with this path. Regards, George -- George Wright, http://www.gwright.org.uk Collabora Ltd - http://www.collabora.co.uk pgph3RDRxcP4W.pgp Description: PGP signature ___ Telepathy mailing list Telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
