# Xcapclient 1.0 released

**URL:** <https://www.ruby-forum.com/t/xcapclient-1-0-released/172928>\
**Category:** Ruby\
**Created:** [July 30, 2009, 2:23am UTC](https://www.ruby-forum.com/t/xcapclient-1-0-released/172928 "2009-07-30T02:23:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [July 30, 2009, 2:23am UTC](https://www.ruby-forum.com/t/xcapclient-1-0-released/172928/1 "2009-07-30T02:23:36Z")

</div>

For those interested in SIP and SIMPLE rich presence:

xcapclient 1.0 has been released

[http://xcapclient.rubyforge.org/](http://xcapclient.rubyforge.org/)  
[http://dev.sipdoc.net/projects/ruby-xcapclient/wiki/](http://dev.sipdoc.net/projects/ruby-xcapclient/wiki/)

## Ruby XCAPClient

A XCAP client library written in Ruby language.

XCAP (RFC 4825) is a protocol on top of HTTP which allows a client  
(usually a  
VoIP/SIP device) to manipulate the contents of Presence Information Data  
Format (PIDF) based presence documents. These documents are stored in a  
server  
in XML format.

Ruby xcapclient library implements the XCAP protocol in client side,  
allowing  
the applications to get, store, modify and delete XML documents in the  
server.

== Features

- Fetch, create/replace and delete a document.
- Fetch, create/replace and delete a document element (XML node).
- Fetch, create/replace and delete an element attribute.
- Full configurable parameters allowing customized fields for each XCAP  
application, such auid, XML namespace, MIME-Type, scope (:user or  
:global) and  
default document name (“index” if not set).
- Fetch the namespaces and prefixes of a document node as they are used  
in the  
server.
- Manage of multiple documents per XCAP application.
- Fetch the XCAP server auids, extensions and namespaces (“xcap-caps”  
application).
- SSL.
- Digest and Basic HTTP authentication.
- Raise custom Ruby exception for each HTTP error response.

---

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [November 9, 2009, 1:03pm UTC](https://www.ruby-forum.com/t/xcapclient-1-0-released/172928/2 "2009-11-09T13:03:10Z")

</div>

For those interested in SIP and SIMPLE rich presence:

xcapclient 1.1 has been released

[http://xcapclient.rubyforge.org/](http://xcapclient.rubyforge.org/)  
[http://dev.sipdoc.net/projects/ruby-xcapclient/wiki/](http://dev.sipdoc.net/projects/ruby-xcapclient/wiki/)

## Changes from version 1.0

Added real support for fetching/creating/replacing/deleting node  
attributes.

The methods get\_element, put\_element, delete\_element and  
get\_element\_namespaces have been removed.  
Instead now we have:

- get\_node
- put\_node
- delete\_node
- get\_attribute
- put\_attribute
- delete\_attribute
- get\_node\_namespaces

* * *

## Ruby XCAPClient

A XCAP client library written in Ruby language.

XCAP (RFC 4825) is a protocol on top of HTTP which allows a client  
(usually a  
VoIP/SIP device) to manipulate the contents of Presence Information Data  
Format (PIDF) based presence documents. These documents are stored in a  
server  
in XML format.

Ruby xcapclient library implements the XCAP protocol in client side,  
allowing  
the applications to get, store, modify and delete XML documents in the  
server.

== Features

- Fetch, create/replace and delete a XML document.
- Fetch, create/replace and delete a XML node.
- Fetch, create/replace and delete a XML node attribute.
- Full configurable parameters allowing customized fields for each XCAP  
application, such auid, XML namespace, MIME-Type, scope (:user or  
:global) and  
default document name (“index” if not set).
- Fetch the namespaces and prefixes of a document node as they are used  
in the  
server.
- Manage of multiple documents per XCAP application.
- Fetch the XCAP server auids, extensions and namespaces (“xcap-caps”  
application).
- SSL.
- Digest and Basic HTTP authentication.
- Raise custom Ruby exception for each HTTP error response.