1.1.2 Simple vs Extended

The fork visible in 1.1.1 (simple query protocol on one side, extended on the other) is the subject of this section, one level deeper. 1.1.1 set the skeleton: simple is one message, extended is four. The job here is to show how that split translates into four distinct outcomes: plan reuse, parameter safety, pipelining, and error handling. Message sequence: the shape of one cycle is different Putting the message sequences side by side makes the difference visible at a glance. Simple : Client Serv