-TODO
-
-The web service solution to use depends a lot on the application requirements. Whether communication footprint is vital? Whether the service needs to published through a discovery service or not? Whether the service functionality needs to be described for other services or clients? For our application a RESTful web service best fitted, mainly because of our protocol simplicity and our need for a low communication overhead. Also a discovery feature was not required.
-
-WS-Security offers a lot of features in comparison with HTTPS with TLS/SSL, like end-to-end communication and message integrity. If this are not required then HTTPS offers a lower overhead and is recommended to be used.
\ No newline at end of file
+We designed and implemented P2P-Tube, a video-sharing platform which supports the new Next-Share content delivery technology from P2P-Next. The most common features needed to implement a video-sharing site are found on this platform which allows users to share their thoughts through videos. It ensures scalability for a few thousands users by using the Next-Share technology, which moves part of the overhead to the users, and by using a distributed system of content ingestion machines (CIS). It offers organization of video assets through categories and social features through users, comments and voting. Community contributions are encouraged, because P2P-Tube is free and open-source.
\ No newline at end of file
projects / living-lab-site.git / blobdiff