-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 01.09.2014 21:12, Tobias Kräntzer wrote: > I’m planning to build a module that combines XMPP-PubSub with > remoteStorage [1].
That sounds like a great project! > The question is, how should the items in the collections be mapped > between the two APIs. remoteStorage is tree based and PubSub is > somehow „list-based“. Isn't PubSub with XEP-248 (PubSub Collection Nodes) also tree based? > > service.example.com ├── folder A │ ├── item 1 │ ├── item 2 │ > ├── subfolder u │ │ └── item x │ └── subfolder v │ └── > item 7 ├── folder B │ ├── subfolder u │ │ └── item x │ └── > item 1 ├── folder C │ └── item y ├── item 1 └── item 2 How about: - - Use collection nodes for folders, and non-collection nodes for files - - Folder collection nodes do not need to have any items - - You can easily determine which node represents a folder and which is a file by doing a disco#info on it and determine it's type, which is either collection or leaf. - - Every node has set pubsub#max_items to '1' - - The item of a file node contains the data of the file (and maybe some metadata) Best, Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQF8BAEBCgBmBQJUByYiXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMzU3QjAxODY1QjI1MDNDMTg0NTNEMjA4 Q0FDMkE5Njc4NTQ4RTM1AAoJEIysKpZ4VI41IG0H/AuJR+HO/vj8uph85x+XlRxs EZcSLf2ZN2p9j1tfGSCrcMKdrG31u9nIvrxJIykjAhYvoFPCaSH0k0Ng2JTQv6ER PvOluiYYvzo2vWjsPYbcr4rrrU7FeFNfVNtMYbYihjWo8wqYNutNdr6fiGh3rOdZ HVrehRCBUB7DuusCB0G3nikED0GrZarHaUcE+XdLpDBg4X0wJLBjjRwFAtGmu372 viBbbMbYaPqL5sb+W5fTIj7izcCEOkkk7BLUSAhcyUyAuvmSi6gplJ+8nAYTzuUj awhWDWe3anN03LlzcIKMGt6lEbD/1BoISGhC9UPUBJypGUefCpOfp00Tn6rsBK8= =i0JZ -----END PGP SIGNATURE----- _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
