> On Sep 1, 2020, at 3:11 PM, Alan Carroll > <solidwallofc...@verizonmedia.com.INVALID> wrote: > > Sorry for chiming in late - > > Note this is extremely similar to IP addresses and I recommend we use the > same solution. That is, there is a class HttpPriority which has just a > type/style/family value and possibly a length. This is an abstract class > like sockaddr (which no one actually instantiates). The family indicates > the concrete type, which is something like Http2Priority or Http3Priority, > etc., just like sockaddr_in and sockaddr_in6. When you call the priority > getter, it returns a HttpPriority* which is a pointer to a concrete > instance, the type of which is determined by the family. Again, just like > getting an IP address from a socket. I assume with class here, you mean a regular C struct ? — Leif
- Re: TS API Review: New HTTP/2 ... Sudheer Vinukonda
- Re: TS API Review: New HTTP/2 ... Brian Neradt
- Re: [E] Re: TS API Review: New... Alan Carroll
- Re: [E] Re: TS API Review: New... Brian Neradt
- Re: [E] Re: TS API Review: New... Brian Neradt
- Re: [E] Re: TS API Review: New... Masaori Koshiba
- Re: [E] Re: TS API Review: New... Sudheer Vinukonda
- Re: [E] Re: TS API Review: New... Masakazu Kitajo
- Re: [E] Re: TS API Review: New... Masakazu Kitajo
- Re: [E] Re: TS API Review: New... Alan Carroll
- Re: [E] TS API Review: New HTT... Leif Hedstrom
- Re: [E] TS API Review: New HTT... Brian Neradt
- Re: [E] TS API Review: New HTT... Brian Neradt
- Re: TS API Review: New HTTP/2 stream id and... Leif Hedstrom
- Re: [E] TS API Review: New HTTP/2 stream id and priority... Walt Karas
- Re: TS API Review: New HTTP/2 stream id and priority get... Bryan Call