From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20101115032531.GB27578@opal.ai.ki> References: <20101115032531.GB27578@opal.ai.ki> Date: Mon, 15 Nov 2010 13:44:26 -0500 Message-ID: Subject: Re: [9fans] 9p vs http From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Topicbox-Message-UUID: 805f3408-ead6-11e9-9d60-3106f5b1d025 You're way off about the merits of pipelining. As far as parallel requests are concerned, the 9P protocol beats HTTP hands down (as does basically any other request response protocol), because it has explicit unique IDs on the requests and responses. That allows a server to respond to two requests in an order different than their arrival order. If you send an expensive HTTP request followed by a cheap one, the server can't tell you the cheap answer until it has told you the expensive answer. The word "pipelining" means "we forgot to put request and response IDs into the protocol so we kludged it in by requiring responses to happen in the same order as requests." If a protocol says it has pipelining, that's always a bad sign. Russ