[Devel] Storage of XCAP profiles

[Daniel-Constantin Mierla]

Hello Adrian,

yes, the schema can (will) be updated. Because now the new presence 
module has support only for presence_rules, there was no need to add 
document type. We look now to add integration with the usrloc and 
emulation of end-to-end presence. The the module will be pushed on cvs, 
meanwhile, for those interested, the new presence server is available 
for beta testers at:

http://openser.org/dokuwiki/doku.php?id=presence:presence-module

Cheers,
Daniel


On 10/07/06 18:20, Adrian Georgescu wrote:
> Hi Daniel,
>
> I took a look the current storage design needed for presence 
> functionality. While trying to port my existing xcap data to the 
> proposed table I run into the following problem.
>
> Per user I already have to store several xcap documents:
>
> presence_rules.xml
> resource-list.xml
> rls-services.xml
>
> The current mysql schema 
>
> CREATE TABLE `xcap_xml` (
>   `user` varchar(64) NOT NULL,
>   `domain` varchar(128) NOT NULL,
>   `xcap` text NOT NULL,
>   PRIMARY KEY  (`user`,`domain`)
> );
>
> does not allow to store multiple documents, the only data I could 
> store is the presence-rules document.
>
> Can we change this to a format that can accomodate multiple xcap 
> documents per user like:
>
> CREATE TABLE `xcap_xml` (
>   `username` varchar(64) NOT NULL,
>   `domain` varchar(128) NOT NULL,
>   `document` varachar(255) not NULL,
>   `content` text NOT NULL,
>   PRIMARY KEY  (`username`,`domain`)
> );
>
>
> Adrian
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel
>