Slashdot Mirror

← Back to Stories (view on slashdot.org)

Features of a post-HTTP Internet?

Posted by Cliff on from the thinking-ahead dept.

Ars-Fartsica asks: "We've been living with HTTP/HTML ("the web") for a quite a while now, long enough to understand its limits for content distribution, data indexing, and link integrity. Automatic indexing, stateful-ness, whole-network views (flyovers), smart caching (P2P), rich metadata (XML), built in encryption, etc are all fresh new directions that could yield incredible experiences. Any ideas on how you would develop a post-HTTP/HTML internet?"

2 of 122 comments (clear)

  1. Forget HTTP. by Spudley · · Score: 5, Interesting

    Forget about replacing HTTP - let's deal with the real problem protocol first: SMTP.

    Please! Someone give us a secure email protocol that doesn't allow address spoofing.

    --
    (Spudley Strikes Again!)
  2. Re:Wrong question. by aklix · · Score: 5, Interesting

    HTTP is a transfer protocal that does everything I need it to do. As for HTML, we practically have a post-HTML internet. DHTML, Javascript, CSS, pretty soon Apple's Canvas. It all works nice and pretty. So why would we need a post HTTP, especially if we have other protocals to do other things.