<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> On 11/16/2010 09:01 PM, Dirk Meyer wrote: <blockquote cite="mid:4CE2E330.5060702@tzi.de" type="cite"> <pre wrap="">Hi, On 16.11.2010 17:35, Jon Kristensen wrote: </pre> <blockquote type="cite"> <pre wrap="">On 11/16/2010 08:32 AM, Dirk Meyer wrote: </pre> <blockquote type="cite"> <pre wrap="">An XMPP-based media server was part of my PhD thesis. If you have a lot of free time: <a class="moz-txt-link-freetext" href="http://elib.suub.uni-bremen.de/diss/docs/00011878.pdf">http://elib.suub.uni-bremen.de/diss/docs/00011878.pdf</a> If you don't, take a look at chapters 2.1, 6 and 7. They contain the use cases for my idea, the generic secure architecture and what you can do with it. </pre> </blockquote> <pre wrap="">Wonderful! I will start reading today! :) </pre> </blockquote> <pre wrap="">That will keep you busy :) </pre> </blockquote> It certainly does keep me busy... But it's an amazing read! Thanks again! :) <blockquote cite="mid:4CE2E330.5060702@tzi.de" type="cite"> <blockquote type="cite"> <pre wrap="">Have you coded anything in regards to this so far? </pre> </blockquote> <pre wrap="">The basic architecture is done including secure Jingle streams based in TLS and IBB. The proof of concept for the Jingle SOCKS5 streams was done by someone else. You can find most of my code in the Freevo SVN in svn://svn.freevo.org/kaa/xmpp (you also need kaa.base which is located in /kaa/base) </pre> <blockquote type="cite"> <pre wrap="">Right now we're actually considering revising the features for 0.1 to only support only "managed media", the higher level system of file(s) and metadata. I'm just thinking about the scope of the project and that there are better tools for remote file systems. An arbitrary file could of course be uploaded using something like a "Object" managed resource, but that's not what the typical use case would be like. What do you think about this? </pre> </blockquote> <pre wrap="">One might think there are remote file systems, but in fact it is not so easy. How do you access a file stored on your home server behind a NAT? How do you make this secure? And how do you prevent someone else you want to give access to one file from accessing all? That is considered in my thesis but not implemented in a ready-to-use way. </pre> </blockquote> Good point! I'm thinking - translating our current vision for Pontarius into XPMN terms - Pontarius 0.1 would consist of software for three XPMN services: photo, audio and video. We also want to try to make controller/interface software for a set as devices such as web browser (implementing as many features as possible in a JavaScript application), some or all major operating systems and possibly also some smartphones like the Android phone (perhaps depending on what happens with Java/Linux and Oracle vs. Google). Would this be redundant in some way? Would this be useful for you, XPMN and the Freevo project? Is there something else you would like to see us do or any other route you think we should take? Thank you! Warm regards, Jon Kristensen </body> </html>