@misc{p2p-next,
howpublished = {{http://www.p2p-next.org/}},
title = {{P2P-Next}},
- note = "[Online, accessed 31-March-2011]"
+ note = "[Online, accessed 2-February-2012]"
}
-@misc{win8-html5,
- howpublished = {{www.microsoft.com/presspass/features/2011/jun11/06-01corporatenews.aspx}},
- title = {{Previewing 'Windows 8'}}
+@misc{ldap,
+ howpublished = {{http://tools.ietf.org/html/rfc4510}},
+ title = {{Lightweight Directory Access Protocol (LDAP)}},
+ year={2006},
+ note = "[Online, accessed 2-February-2012]"
}
+@misc{vlc,
+ howpublished = {{http://www.videolan.org/vlc/}},
+ title = {{VideoLAN}},
+ note = "[Online, accessed 2-February-2012]"
+}
+
+@article{openid, title={OpenID Authentication 2.0}, url={http://openid.net/specs/openid-authentication-2_0.html}, journal={OpenID Foundation}, author={Brad Fitzpatrick}, year={2007}}
+
@misc{w3c-ws-gloss,
howpublished = {{http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211/}},
title = {{W3C Web Services Glossary}}
%\textbf{\textit{Keywords -- ala, bala, portocala}}
\begin{IEEEkeywords}
-Web Service, Security
+Video-On-Demand, NextShare, P2P-Next
\end{IEEEkeywords}
%\IEEEpeerreviewmaketitle
+++ /dev/null
-% vim: set tw=78 sts=2 sw=2 ts=8 aw et ai:
-\documentclass[conference]{IEEEtran}
-
-\usepackage{ucs}
-\usepackage[utf8x]{inputenc}
-\usepackage[english]{babel}
-%\usepackage{hyperref} % use \url{http://$URL} or \href{http://$URL}{Name}
-\usepackage{underscore} % underscores need not be escaped
-\usepackage{subfigure}
-\usepackage{verbatim}
-\usepackage{float}
-\usepackage{amsmath, amsthm, amssymb}
-
-% Support for including graphics
-\usepackage{graphicx}
-\DeclareGraphicsExtensions{.pdf,.png,.jpg}
-
-\usepackage[outerbars,color]{changebar}
-\cbcolor{red}
-
-\let\Oldcbstart\cbstart
-\let\Oldcbend\cbend
-%\renewcommand{\cbstart}{\color{red}\Oldcbstart}
-%\renewcommand{\cbend}{\Oldcbend\color{black}}
-\renewcommand{\cbstart}{}
-\renewcommand{\cbend}{}
-
-\begin{document}
-
-\title{P2P-Tube: A Video Sharing Web Platform Based on NextShare Technology}
-
-\author{\IEEEauthorblockN{Călin-Andrei Burloiu}
-\IEEEauthorblockA{Automatic Control and Computers Faculty\\
-University Politehnica of Bucharest\\
-Emails: calin.burloiu@gmail.com}}
-
-\maketitle
-
-\begin{abstract}
-\input{src/abstract}
-\end{abstract}
-
-%\textbf{\textit{Keywords -- ala, bala, portocala}}
-
-\begin{IEEEkeywords}
-Web Service, Security
-\end{IEEEkeywords}
-
-%\IEEEpeerreviewmaketitle
-
-\section{Introduction} % Călin
-\label{sec:introduction}
-\input{src/introduction}
-
-\section{Web Services} % Vali
-\label{sec:web-services}
-\input{src/web-services}
-
-\section{Security Solutions for Web Services} % Vali
-\label{sec:security-solutions}
-\input{src/security-solutions}
-
-\section{P2P-Tube video platform} % Călin
-\label{sec:p2p-tube}
-\input{src/p2p-tube}
-
-\section{Implementation} % Călin
-\label{sec:implementation}
-\input{src/implementation}
-
-\section{Conclusion} % Călin
-\label{sec:conclusion}
-\input{src/conclusion}
-
-\section*{Acknowledgment}
-\label{sec:acknowledgment}
-
-Special thanks go to the P2P-Next~\cite{p2p-next} team who is working
-enthusiastically to deliver the next generation peer-to-peer content delivery
-platform. Their dedication, professionalism and vision are a constant factor
-of motivation and focus for our work.
-
-\bibliographystyle{abbrv}
-\bibliography{p2p-tube}
-
-\end{document}
-TODO ... a scalable video sharing web platform, named P2P-Tube. Part of the European project P2P-Next, our platform aims to be a complete web solution for the next generation video sharing technology, which is NextShare.
\ No newline at end of file
+In this paper we propose P2P-Tube, a video sharing web platform, similar with YouTube, which uses Next-Share, a video sharing technology developed within European project P2P-Next. This project's goal is to build the next generation peer-to-peer content delivery platform. Next-Share is based on two browser plugins which provide video-on-demand and live streaming through BitTorrent peer-to-peer protocols. Users are able to retrieve video content not only from a number of delivery servers, which assume the role of \textit{seeders}, but also concomitantly from other users, which are \textit{leechers}.
\ No newline at end of file
-Since the emergence of the web the way applications are designed has changed. User interfaces are migrating to HTML-based solutions, in conjunction with CSS and JavaScript, for example Windows 8 will be based on HTML5 \cite{win8-html5}. More and more applications are migrating to the cloud being accessed thorough a web browser interface, for example Google Docs is a web-based alternative to the desktop Microsoft Office. Following this flow, communication protocols have also adhered to the new web paradigm, through the emergence of \textit{web services}, which implement communication on top of existing application protocols, like HTTP and its WWW protocol stack.
+Part of our work at the European project P2P-Next \cite{p2p-next} is P2P-Tube, a web platform which aims to be a complete solution for video sharing, video-on-demand and live streaming through Next-Share (TODO: cite D4.0.6) content delivery platform. Users are able to watch videos through one of the two Next-Share browser plugins, one based on HTML5 and the other based on VLC \cite{vlc}. They can sign up for an account using three different ways of authentication: internal P2P-Tube authentication, authentication through LDAP \cite{ldap} or through OpenID \cite{openid}, using a third-party account. Logged in users can share their thoughts by uploading new video assets. Social interaction between them is possible through the possibility of commenting each other's videos and voting them with likes and dislikes.
-The main advantages of web services are interoperability and their small implementation overhead. Being built over standard protocols like HTTP, a lot of libraries already support it and the main communication primitives are already implemented. Thus developers do not need to handle this aspects and can focus on specific protocol requirements. In comparison, the standard approach of sending protocol messages directly over TCP or UDP, requires an additional development overhead every time basic communication primitives are being implemented.
+In order to make P2P-Tube scale to a large amount of users which are concurrently uploading new video assets, we have designed a distributed system which uses one or more Content Ingestion Servers (CIS). Their role is to prepare uploaded videos for sharing with other users and make those videos available on the platform. We have chosen web services as the way of communication between web servers, which deliver P2P-Tube application to the users, and Content Ingestion Servers.
-Part of our work to the European project P2P-Next \cite{p2p-next} is P2P-Tube, a video sharing web platform for deploying sites like YouTube. P2P-Next goal is to build the next generation Peer-to-Peer content delivery platform. NextShare technology facilitates video streaming through BitTorrent and peer-to-peer protocols. Users are able to download video content not only from a number of delivery servers, which assume the role of \textit{seeders}, but also concomitantly from other users, which are \textit{leechers}. P2P-Tube platform uses this technologies in a set of browser plugins which are capable of providing video-on-demand and live streaming.
-
-Applications built on top of P2P-Tube, need to offer users the possibility of uploading new videos. In order to make the application scale to a large amount of users which are concurrently doing this, we have designed a distributed system which uses one or more Content Ingestion Servers (CIS). Their role is to prepare uploaded videos for sharing with other users and make those videos available on the platform. We have chosen web services as the way of communication between web servers, which deliver the P2P-Tube application to the users, and Content Ingestion Servers.
-
-In Section \ref{sec:web-services} we present state of the art solutions for web services. Section \ref{sec:security-solutions} introduces ways to secure those web services. P2P-Tube platform is presented in Section \ref{sec:p2p-tube} and implementation of security into CIS in Section \ref{sec:implementation}. An analysis of the reasons behind our choice for a particular web service technology and a particular security solution is also presented here. We conclude this article in Section \ref{sec:conclusion}.
\ No newline at end of file
+Next-Share technology and plugins used in our platform are presented in \S \ref{sec:next-share}. P2P-Tube platform design architecture and implementation are presented in \S \ref{sec:design} and \S \ref{sec:implementation}, respectively. We conclude this article in \S \ref{sec:conclusion}.
\ No newline at end of file
-TODO
\ No newline at end of file
+P2P-Next is an FP7 European project made up by a consortium of academic and industrial players which aim to build the next generation \textit{peer-to-peer (P2P)} content delivery platform. 21 partners from 12 different countries are involved here: BBC, Technische Universiteit Delft, Pioneer, Technical Research Center of Finland and also University Politehnica of Bucharest, were P2P-Tube platform was developed. P2P-Next takes as design principals the usage of open standards, open source development and future proof iterative integration.
+
+In the last ten years two emerging trends sparkled the evolution of Internet: first of all more and more users share their content through social networks and P2P systems and secondly video sharing, video-on-demand and live streaming are increasingly gaining popularity. The current Internet infrastructure was not initially designed for simultaneous transmission of live events to millions of people and proposed technologies like multicasting do not seem to solve the problem. Television is no longer the main medium for audio and visual information content. Motivated by all these fact, P2P-Next started research and development of a new multimedia infrastructure base on both P2P technologies like BitTorrent and video streaming.
+
+Next-Share is the name of the content delivery technology provided by P2P-Next which enables features such as on-demand video and live video for both computers and STBs (digital set-top-boxes) usable with TVs.
+
+Next-Share platform implements its core functionality into NextShareCore which is written in Python. Video rendering in a PC browser using Next-Share can be done with two types of plugins: SwarmPlayer and NextSharePC.
+
+A de facto standard today for playing videos in a browser is Adobe Flash Player. Because this is a proprietary technology and P2P-Next uses open standards other technologies needed to be explored. W3C (World Wide Web Consortium) currently works at a new version of HTML, HTML5, which supports, besides other revolutionary features, audio and video tags. Thus video files can be easily embedded into web pages, just like images, without any browser extensions or plugins. Although HTML5 is still a draft, most modern browsers already implement some of its features including video and audio tags. On this background, non-profit organizations and big corporations have engaged in a codec war. Some of the problems were whether to accept or not proprietary condecs, which codecs should standardly accepted etc.. For instance Microsoft promotes AVC / H.264, a proprietary video codec. Despite of its image quality and its good compression ratio, non-profit organization criticized it for being proprietary and closed standard. As a consequence Ogg containers with Vorbis audio codec and Theora video codec were included into HTML5. Google also stepped into this war and acquired On2 Technologies, for VP8, an open video compression format. They proposed WebM containers with Vorbis audio compression and VP8 video compression. Because Google's proposal is a free open standard it was accepted into HTML5 along with Ogg (Vorbis + Theora). Currently most modern browsers support video tags with Ogg and WebM containers.
+
+P2P-Next developed \textbf{SwarmPlayer}, a Next-Share compliant browser plugin which is based on HTML5. It is currently supported in Windows in Mozilla Firefox as an extension and in Internet Explorer and there is also a Mac version.
+
+Because only a few video formats are supported in HTML5 and older browsers do not support HTML5 video tags P2P-Next developed another variant of its Next-Share plugin, named \textbf{NextSharePC}. This one is based on VLC Player libraries to render videos and is able to play a lot of video formats, basically anything that is support by VLC Player. Written by the VideoLAN project, VLC Media Player is a free open source cross-platform multimedia player and framework. Its disadvantage is that it is currently supported only in Windows, for both Mozilla Firefox, as a plugin, and Internet Explorer.
+
+A NextShare plugin consists of two major parts: the browser plugin / extension, running in the browser address space and the Next-Share Agent API which facilitates communication with the NextShareCore.
\ No newline at end of file
projects / living-lab-site.git / commitdiff