Browse Prior Art Database

Peer to peer and traditional webserver combination

IP.com Disclosure Number: IPCOM000238144D
Publication Date: 2014-Aug-05
Document File: 2 page(s) / 33K

Publishing Venue

The IP.com Prior Art Database

Abstract

In a traditional web environment, both the site framework (html, javascript) and data (user records) are stored on the server, and when the website is visited, both are served from the server to a web browser (client). This article describes an alternative approach, where the framework remains on the web server - but the users keep data on their local machines, and the server only points to data. When the website is visited, the site framework comes from the server, and the data comes via a peer-to-peer connection, from other "online" machines. This mechanism would work particularly well for sharing profiles in a social network.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 70% of the total text.

Page 01 of 2

Peer to peer and traditional webserver combination

In the example of a social network (eg Facebook), today, all data is stored on the central server. This means that a user doesn't know who has access to it.

    In order to retain control over data without having to trust that the central service provider will not share it (or be hacked), it may be desirable to keep this data locally. This article shows how we can get generic files (eg css / images etc) from a central webserver (ie the files which would be the same for everyone), and content data (personal data) from a peer to peer connection from the data owner.

    This is different from Content Delivery Networks in that we are being specific in who we share our data with, and the data originates from the data owners local disk.

    Users register their ids on a central social networking site (for example) and keep their data locally. It would be implemented using a traditional webserver, which would supply enough information to set up a peer to peer link between the requestor of the information and the data owner.

    Both user A and B would have registered on the central server, and a unique address which identifies them enough to create a WebRTC connection, would be stored in the registry on the server.

    When user A visits the central server, and attempt to view User B's profile, the central server would download to User A's machine the appropriate files to set up the template page (eg html/css/images etc) and also some Web...