Group :: Rede/Mensagens instantâneas
RPM: tapioca-glib
Navegação
Principal Changelog Spec Patches Sources Download Gear Bugs e FR Repocop
A versão atual: 0.14.1.2-alt3.qa1
Data da compilação: 19 abril 2013, 22:18 ( 573.8 weeks ago )
Tamanho:: 129.19 Kb
Home page: http://tapioca-voip.sourceforge.net/wiki/index.…
Licença: LGPLv2+
Sumário: A framework for Voice over IP (VoIP) and Instant Messaging (IM)
Descrição:
Lista dos contribuidores Lista dos rpms provida por esta srpm:
ACL:
Data da compilação: 19 abril 2013, 22:18 ( 573.8 weeks ago )
Tamanho:: 129.19 Kb
Home page: http://tapioca-voip.sourceforge.net/wiki/index.…
Licença: LGPLv2+
Sumário: A framework for Voice over IP (VoIP) and Instant Messaging (IM)
Descrição:
Tapioca is a framework for Voice over IP (VoIP) and
Instant Messaging (IM). Its main goal is to provide
an easy way for developing and using VoIP and IM
services in any kind of application. It was designed
to be cross-platform, lightweight, thread-safe, having
mobile devices and applications in mind.
Tapioca's main goals are:
* Create a solution that integrates all components
used by VoIP and IM applications in a single, reliable
and easy to use framework, which is able to work on different
platforms.
* Spare resources, providing central services for multiple
applications. Eg.: The control of all incoming and outgoing SIP
requests are managed by the SIP service, avoiding the creation of
one SIP stack and allocation of a network port for each SIP-based
application.
* Reduce the overhead of control layers and library dependencies.
Mantenedor currente: Eugeny A. Rostovtsev (REAL) Instant Messaging (IM). Its main goal is to provide
an easy way for developing and using VoIP and IM
services in any kind of application. It was designed
to be cross-platform, lightweight, thread-safe, having
mobile devices and applications in mind.
Tapioca's main goals are:
* Create a solution that integrates all components
used by VoIP and IM applications in a single, reliable
and easy to use framework, which is able to work on different
platforms.
* Spare resources, providing central services for multiple
applications. Eg.: The control of all incoming and outgoing SIP
requests are managed by the SIP service, avoiding the creation of
one SIP stack and allocation of a network port for each SIP-based
application.
* Reduce the overhead of control layers and library dependencies.
Lista dos contribuidores Lista dos rpms provida por esta srpm:
- tapioca-glib
- tapioca-glib-debuginfo
- tapioca-glib-devel
- tapioca-glib-devel-doc