1 / 15

The Two-Way Web An Interoperable Foundation for P2P

The Two-Way Web An Interoperable Foundation for P2P. Rohit Khare CEO, KnowNow Inc. 14 February 2001 O’Reilly P2P Conference. Introduction. What infrastructure services do we need to build great P2P applications? Can today’s One-Way Web infrastructure provide all of those services?

kolya
Download Presentation

The Two-Way Web An Interoperable Foundation for P2P

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Two-Way WebAn Interoperable Foundation for P2P Rohit Khare CEO, KnowNow Inc. 14 February 2001 O’Reilly P2P Conference

  2. Introduction • What infrastructure services do we need to build great P2P applications? • Can today’s One-Way Web infrastructure provide all of those services? • Can tomorrow’s Two-Way Web overcome perceived limitations and support compelling peer-to-peer applications? The Two-Way Web for P2P

  3. P2P Foundation Services • Transport • Of XML and SOAP, messages, in particular • Security • Using SSL/TLS and some flavor of PKI • Transfer • Of instant messages and multimedia files • Namespaces • Requires fully decentralized management The Two-Way Web for P2P

  4. The P2P Standards “Race” • Entrant Cynic’s View* • Napster “Open” • Gnutella “Chatty” • Groove “Closed” • Invisible Worlds “Rocket Science” • Web Browser “Ugly & Buggy” • * These are all unfair caricatures, to be sure! The Two-Way Web for P2P

  5. Why reuse the Web? 1/2 • Transport • HTTP is the most widely supported application layer protocol on the Internet • SOAP bindings already exist • Security • Web security standards have proven sufficient for multi-billion dollar industries • Integration & Management are the true challenges; Web infrastructure already exists The Two-Way Web for P2P

  6. Why reuse the Web? 2/2 • Transfer • Almost every P2P service already standardized on HTTP for file transfer • Byte-ranges allow restart of interrupted xfers • Chunked-encoding allows streaming data • Namespaces • URIs extend the domain naming system to all • Same social foundation as XML Namespaces The Two-Way Web for P2P

  7. Benefits of reusing the Web • Caching • HTTP/1.1 has robust caching semantics • Format Negotiation • Allows both parties to choose media types • Proxying • Clearly demarcates security & trust boundary • Evolution • Leverage continuing work on WebDAV, XP,… The Two-Way Web for P2P

  8. Costs of reusing the Web • User Interface • The “submit” and “refresh” buttons suck • Applets and Flash are too low-level • Full-scale downloads severely inhibit adoption & inflate total costs of ownership • Firewalls • Vast majority of end-users cannot accept inbound IP traffic, on port 80 or otherwise The Two-Way Web for P2P

  9. Perceived Limitations • The One-Way Web isn’t enough! • Today’s HTTP tools are fundamentally crippled for peer-to-peer applications: • One-Way • There’s no asynchronous callback-channel • One-to-One • Can’t “multicast” a query to nearest neighbors • One-Shot • Entire transaction fails if a single server fails The Two-Way Web for P2P

  10. Two-Way Web solutions • These are only limitations of the tools… • Using HTTP in both directions* makes it: • Two-Way • We can POST back to a microserver on any device • Any-to-Any • A smart proxy can become the “client” of several other web services without modification • Reliable • A queuing proxy can even operate offline • * This is also known as “Distributed HTTP” per Udell. The Two-Way Web for P2P

  11. KnowNow’s Two-Way Web • We’re building a new generation of commercial Layer 7 Routers • Interconnecting Web services in real-time across HTTP, WAP, SMTP, FTP, IMAP,… • We’re building a new class of Real-time Web applications • “eBay takes longer to reload a page than an entire multi-million dollar bond auction” The Two-Way Web for P2P

  12. Why We Bet on the Web Zero-Install Works with any 4.x+ Web browser (Over 90% share) Works with any HTTP/1.1 Web server, esp. Apache (Over 60% share) Web Developer Community Leverages skills with current scripting languages and design tools Enterprise Apps are Web Apps Leverages current investments in Web/XML ‘adaptors’ Minimizes Integration Costs Leverages existing solutions for Web security, caching, firewalls... The Two-Way Web for P2P

  13. Who else is betting on SOAP Services? Microsoft.NET Sun ONE HP E-Speak IBM WebSphere W3C’s XML Protocol WG Gartner Group predicts that 75% of distributed enterprise application development will use XML messaging by 2004 Real-time peer-to-peer XML message-passing is a fundamental architectural style for Internet-scale apps The Future of InternetApplication Development The Two-Way Web for P2P

  14. Event Notification isn’t at Internet-Scale… yet • KnowNow comes upon the heels of 20 years’ research in event-based integration • Publish-and-Subscribe is already the basis of a $50 Billion software segment • But no current event bus works as well outside the Enterprise LAN firewall • The next e-business challenge is “Leveraging resources you can’t own” The Two-Way Web for P2P

  15. For More Information… • Rohit@KnowNow.com+1 (650) 561-0246 • KnowNow, Inc.2730 Sand Hill RoadSuite 150Menlo Park, California 94025 • We’re Hiring! • (heck, even Fred Sánchez!) The Two-Way Web for P2P

More Related