Function parsePackRequest

This parses the clients request into a list of wants', 'haves', and capabilities. 'wants' indicate objects that the client found and wants from the reference discovery phase. Generally this will be list of objects that references point to. It will not include all objects within that reference's branch. 'haves' indicate objects that the client has and doesn't need sent over by the server. It's used by the sever to decide which objects to send. capabilitiesis a list of features the client wants. In our simplified implementation, none of these are really used since we default to just handlingside-band-64k` for sending data. In the future we'll have to support the capability for the client to push data.

Clients MUST NOT reuse or revalidate a cached response. Servers MUST include sufficient Cache-Control headers to prevent caching of the response.

Servers SHOULD support all capabilities defined here.

Clients MUST send at least one "want" command in the request body. Clients MUST NOT reference an id in a "want" command which did not appear in the response obtained through ref discovery unless the server advertises capability allow-tip-sha1-in-want or allow-reachable-sha1-in-want.

  compute_request   =  want_list
                       have_list
                       request_end
  request_end       =  "0000" / "done"
  want_list         =  PKT-LINE(want SP cap_list LF)
                       *(want_pkt)
  want_pkt          =  PKT-LINE(want LF)
  want              =  "want" SP id
  cap_list          =  capability *(SP capability)
  have_list         =  *PKT-LINE("have" SP id LF)
Copy