Re: [GnomeMeeting-devel-list] [3d round] Dbus' future in gnomemeeting
- From: Jan Schampera <jan schampera web de>
- To: GnomeMeeting development mailing list <gnomemeeting-devel-list gnome org>
- Subject: Re: [GnomeMeeting-devel-list] [3d round] Dbus' future in gnomemeeting
- Date: Tue, 18 Oct 2005 12:45:30 +0200
On Tue, 18 Oct 2005 06:40:39 +0200
Julien PUYDT <jpuydt free fr> wrote:
> > * "GetSupportedProtocols"
> > in : nil
> > out : list of strings (example: "SIP", "H323")
>
> And just after sending that mail I cvs up and see Damien committed the
> following :
> * src/accounts.cpp: Use H.323 instead of H323 as protocol name.
>
> so make the examples "SIP" and "H.323"...
Does it make sense to use the protocol names for URI schemes? Also
watching what future might bring.
That would be like:
URI protocol field protocol reference
sip SIP [RFC3261]
sips SIPS (TLS) [RFC3261]
h323 H.323 [RFC3508] [ITU-T_H.323/4]
tel <unspec> [RFC3966] (see below)
Remarks to "tel" URI scheme:
The "tel" URI describes a service, reaching a telephone number, that
is independent of the means of doing so. That is why there is no
specified underlying protocol. The call can be made vis SIP, H.323, with
prior ENUM resolving.
[RFC3261]: RFC 3261 "SIP: Session Initiation Protocol", June 2002
[RFC3508]: RFC 3585 "H.323 Uniform Resource Locator (URL) Scheme
Registration", April 2003
[RFC3966]: RFC 3966 "The tel URI for Telephone Numbers", December 2004
[ITU-T_H.323/4]: ITU-T Recommendation H.323v.4 "Packet-based multimedia
communications systems", November 2000
Awaiting flames...
Jan
--
"Be liberal in what you accept, and conservative in what you send."
- J. B. Postel, master of the net.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]